<commit_before>---
layout: post
title: "BCDevExchange Adopts Agile"
date: 2015-03-13 21:45:00
creator: "Wrate, <NAME>:EX"
description: "The BCDevExchange Team The BCDevExchange development team has adopted the Agile Methodology and Lean startup theory. To better guide our development work we are inviting users to join in with us and become part of the BCDevExchange community. Getting Agile We empowered the development team to work in 2-week &#8230;"
---
<p><span style="color: #000000"><a href="http://blog.data.gov.bc.ca/wp-content/uploads/2015/03/Scrum_task_board.jpg"><img class="alignright wp-image-3001 size-medium" src="http://blog.data.gov.bc.ca/wp-content/uploads/2015/03/Scrum_task_board-224x300.jpg" alt="Scrum_task_board" width="224" height="300" srcset="http://blog.data.gov.bc.ca/wp-content/uploads/2015/03/Scrum_task_board-224x300.jpg 224w, http://blog.data.gov.bc.ca/wp-content/uploads/2015/03/Scrum_task_board-767x1024.jpg 767w, http://blog.data.gov.bc.ca/wp-content/uploads/2015/03/Scrum_task_board.jpg 887w" sizes="(max-width: 224px) 100vw, 224px" /></a>By <NAME>, Product Owner &#8211; The BCDevExchange Team</span></p>
<p><span style="color: #000000">The <a href="http://bcdevexchange.org/#/home">BCDevExchange</a> development team has adopted the Agile Methodology and Lean startup theory. To better guide our development work we are inviting users to join in with us and become part of the BCDevExchange community.</span></p>
<p><span style="color: #000000"><strong>Getting Agile</strong></span></p>
<p><span style="color: #000000">We empowered the development team to work in 2-week sprints, problem solving and delivering software features that users can test. These software features will be minimum viable products – just enough working software for users to test whether they like it.</span></p>
<p><span style="color: #000000"> We believe it’s better to ‘fail fast’ and that user experience (UX) research and design is fundamental to getting things right. We want the UX work to provide quality assurance up-front and be timed to feed into the development team’s sprint planning sessions.</span></p>
<p><span style="color: #000000"><strong>Hearing the User</strong></span><br />
<span style="color: #000000"> We are initiating the formation of two user groups to give us feedback at the tactical level. One group will help us imagine and design the future of the product. Our plan is to convene this group and workshop the construction of a product backlog to help us imagine what the product will look like in six months.</span></p>
<p><span style="color: #000000"> We are looking for interested people who can contribute to the future design and who will grow with us as the BCDevExchange matures. For optimal use of their time, we figure the community needs to come together every three months or so.</span></p>
<p><span style="color: #000000"> A second group is intended to evaluate what we’ve done and provide user experience feedback on newly-minted software features created by the BCDevExchange development team. They will test the specifics of what we have developed, and let us refine the product we are making.</span></p>
<p><span style="color: #000000"><strong>Get Involved</strong></span><br />
<span style="color: #000000"> How can you get involved?</span></p>
<p><span style="color: #000000"> We are looking for developers and UX designers to join and help us evaluate work on-the-fly housed in GitHub and on the software features within the BCDevExchange website. We’ll be looking to form this community in the ensuing few weeks. <a href="mailto:<EMAIL>">Contact us</a> if you are interested.</span></p>
<p><span style="color: #000000"> And please tell us your thoughts by leaving a comment on the blog. Does this agile approach resonate?</span></p>
<commit_msg>Remove byline in description<commit_after>---
layout: post
title: "BCDevExchange Adopts Agile"
date: 2015-03-13 21:45:00
creator: "Wrate, David GCPE:EX"
description: "The BCDevExchange development team has adopted the Agile Methodology and Lean startup theory. To better guide our development work we are inviting users to join in with us and become part of the BCDevExchange community. Getting Agile We empowered the development team to work in 2-week &#8230;"
---
<p><span style="color: #000000"><a href="http://blog.data.gov.bc.ca/wp-content/uploads/2015/03/Scrum_task_board.jpg"><img class="alignright wp-image-3001 size-medium" src="http://blog.data.gov.bc.ca/wp-content/uploads/2015/03/Scrum_task_board-224x300.jpg" alt="Scrum_task_board" width="224" height="300" srcset="http://blog.data.gov.bc.ca/wp-content/uploads/2015/03/Scrum_task_board-224x300.jpg 224w, http://blog.data.gov.bc.ca/wp-content/uploads/2015/03/Scrum_task_board-767x1024.jpg 767w, http://blog.data.gov.bc.ca/wp-content/uploads/2015/03/Scrum_task_board.jpg 887w" sizes="(max-width: 224px) 100vw, 224px" /></a>By <NAME>, Product Owner &#8211; The BCDevExchange Team</span></p>
<p><span style="color: #000000">The <a href="http://bcdevexchange.org/#/home">BCDevExchange</a> development team has adopted the Agile Methodology and Lean startup theory. To better guide our development work we are inviting users to join in with us and become part of the BCDevExchange community.</span></p>
<p><span style="color: #000000"><strong>Getting Agile</strong></span></p>
<p><span style="color: #000000">We empowered the development team to work in 2-week sprints, problem solving and delivering software features that users can test. These software features will be minimum viable products – just enough working software for users to test whether they like it.</span></p>
<p><span style="color: #000000"> We believe it’s better to ‘fail fast’ and that user experience (UX) research and design is fundamental to getting things right. We want the UX work to provide quality assurance up-front and be timed to feed into the development team’s sprint planning sessions.</span></p>
<p><span style="color: #000000"><strong>Hearing the User</strong></span><br />
<span style="color: #000000"> We are initiating the formation of two user groups to give us feedback at the tactical level. One group will help us imagine and design the future of the product. Our plan is to convene this group and workshop the construction of a product backlog to help us imagine what the product will look like in six months.</span></p>
<p><span style="color: #000000"> We are looking for interested people who can contribute to the future design and who will grow with us as the BCDevExchange matures. For optimal use of their time, we figure the community needs to come together every three months or so.</span></p>
<p><span style="color: #000000"> A second group is intended to evaluate what we’ve done and provide user experience feedback on newly-minted software features created by the BCDevExchange development team. They will test the specifics of what we have developed, and let us refine the product we are making.</span></p>
<p><span style="color: #000000"><strong>Get Involved</strong></span><br />
<span style="color: #000000"> How can you get involved?</span></p>
<p><span style="color: #000000"> We are looking for developers and UX designers to join and help us evaluate work on-the-fly housed in GitHub and on the software features within the BCDevExchange website. We’ll be looking to form this community in the ensuing few weeks. <a href="mailto:<EMAIL>">Contact us</a> if you are interested.</span></p>
<p><span style="color: #000000"> And please tell us your thoughts by leaving a comment on the blog. Does this agile approach resonate?</span></p>

{'fraction_non_alphanumeric': 0.11081932773109243, 'fraction_numerical': 0.0470063025210084, 'mean_word_length': 5.223039215686274, 'pattern_counts': {'":': 0, '<': 134, '<?xml version=': 0, '>': 134, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '928165', 'n_tokens_mistral': 2418, 'n_tokens_neox': 2097, 'n_words': 931}