Read it in 4 Mins
Agile projects are driven by the need for continuous progress and by the need of making that progress visible. Progress made is made visible through the different agile project management tools used, such as JIRA, Trello, TFS, RTM or even using a simple MS Excel tracking sheet. In this article I am going to discuss about two key statuses that can be seen in an agile project environment.
The ‘Ready’ status in agile projects has its own definition and explanation. Imagine a young lady getting ready to go for an evening wedding. She would spend a good two to three hours getting ready starting for a wash, a facial, a makeup, wearing the dress, hair dressing to wearing jewelry and so on. There is a list of tasks that she’d go through in her head before finally coming out of her dressing room confidently telling her husband, ‘Honey, I’m ready!!’. ☺
Getting ‘Ready’ in Agile is no different and is related to requirements. Specifically it is with regards to user stories, which are the primary form of documentation of requirements in, Agile. All user stories that have been considered as ‘potential candidates’ for the upcoming sprint MUST be in ‘Ready’ status before the team meets up for the Sprint Planning session.
How can we confidently say that the requirements are ‘Ready’ for implementation? It is more of a gut feeling rather than something set in stone. It is subjective and may differ from team to team. It can be identified as when the team is confident enough to say that they have adequate information to start designing and implementing the selected user story.
The following can be a possible checklist that can be used to check the readiness of a story. Again, this is not set in stone. The team is free to define their own checklist for this purpose.
Note: Development team in Agile projects does not mean only the dev team but includes everyone in the implementation team
The above mentioned checklist can be checked as a guideline for any given user story. If the team agrees that all criteria have been ticked then it means that the user story is ready for consideration during the upcoming sprint.
Note again that above is just a guideline. For example, the checklist of another team may not have the checklist item of having the UI / UX completed for the story but they may take it up as a task to be done during the sprint.
While the definition of ready is being proactive, the definition of done is essential to validate that the feature defined in the story has been implemented properly.
Same as with the definition of ‘Ready’, the status ‘Done’ for user stories has a different meaning in an agile environment. For any feature implemented to be deployed into a production environment, the user story MUST be in ‘Done’ state.
Once the aforementioned checklist is checked for any user story implemented during the sprint, that user story may be marked as ‘Done’ if no more work is pending for the same.
If any of the items on the checklist are not complete, ideally the story should not be marked as ‘Done’. It simply means that the feature implementation has not gone through all the stage gates in place to ascertain whether the feature has been implemented properly. However, with the discretion of the customer or the product owner, the team may agree to mark a story as ‘Done’ even if a story has not passed through all the stage gates in the checklist. However, this is not recommended but must be done only if everyone is in agreement.
10 Oct 2018
20 Dec 2018
16 Mar 2021
22 Oct 2019
19 Sep 2019
12 Sep 2020