So, some may say definition of ready. Ready for what, dressed, eaten, going out on the lash? Well in this blog I'm talking in respect to Agile Development and in particular to SCRUM.
At the moment I am a working SCRUM Master and so this is something I have to deal with on a daily basis. In reality its down to your team to decide if something is ready or not but daily hits I get from the team is something is blocked because require info. So, obviously the team thought was in a ready state but it was not.
So, what is the definition of ready? Well, an story is ready when every member of your team can understand the problem, understand steps on how to reproduce and understand the test procedure. But what do I mean when understand the problem? Well, every team member should be able to ready the story description, understand what needs to be done and not have any questions (other than maybe some minor ones that can be asked to the PO) and to be able to go away and code.
How often does this happen, well seems not so in my experience. My team for my current sprint, as an example, decided to stick to this for our current sprint and rejected every story in the product backlog! Now or course this is the domain of the PO; but does effect the team as no work to start.
So, if this is the case, should you stick to your guns on this matter? Yes is the short answer. If you are to ensure you get quality ready stories that is. Work can always be resolved ongoing but by accepting non-ready items into a sprint you can not make commitment to PO.
Anyhow, this is really just by blog/rant on the matter as its been a major headache to me in the past. If this is something you have also had or have comments or additions to definition please do add..
No comments:
Post a Comment