miércoles, 10 de septiembre de 2014

WhiteBoard for Our Stories and Acceptance Criteria

Hi readers, on my last post I talk about acceptance criteria y and user stories, now we are gonna talk about how to make a whiteboard with stages that can help us for has a better administration of our projects:



In the last picture, we can see four areas, this areas in fact represent our stages of the development of software. Let's explain some more of that:

  • Backlog: On this stage we are gone to put our user stories, this stories are a weak idea of the requirements of project that we want to complete on the paper. For start this stories we used the templates of the user stories and the acceptance criteria for begin given an structure to the requierements of the project.
  • Ready: This stage on the whiteboard represent all the stories that has an acceptable story and acceptance criteria. In this moment our stories are a guide for our project, and help us write code more clearly and efficient.
  • Working: In this stage the development team put the stories that their are developing on real time. The user stories are complete and the acceptance criteria satisfy the requirements of the project and the user.
  • Completed: Here the user stories are complete and functional. The team has develop succesfuly the requirements of last stage and get closer to finish the project.

Use the format of SCRUM give to the team a global vision of the project. Made weekly reunions help to empowerment the team, so this help to mark a specific way to complete the goal. Something than is very useful is keep in mind the acronym DRY, that means "Don't Repeat Yourself", because this guide us for make the things just once, this help us for make the code: better, faster, and more efficient.


0 comentarios:

Publicar un comentario