In the Scrum methodology you have 30 calendar days to a sprint (usually). This means 22 working days. We assume a 30% maintenance burden which breaks down into fixing bugs on shipping product, helping Product Owner with next sprint, and other distractions. That leaves about 16 days for each team member. Of this 16 days, some team members will have time off and other distractions leaving you with an average of 10-12 days per team member on any given sprint.
We heard from all the teams recently in Sprint Retrospectives and while some believed the small chunks were a hindrance to real productivity and doing the right thing (design phase - I’ll talk about this in another post soon), others felt that the small chunks were easy to focus on and understand. I think I will take focus and understanding that ends in working software instead of the entire team still being stuck in design review meetings at the end of 30 days.
The lesson here is keep the deliverables very small and you will succeed in both creating something of value and high quality as well as something the whole team (including traditional doc and qa resources) completely understands.
Scrumfully yours,
Corey
Leave a Reply
You must be logged in to post a comment.