By: Itay Maman
My deviation: Instead of story estimation I introduced “story matching”: we take each story from this Sprint and try to match it with a story (or several stories) from the last sprint. Pros: (1) Easier...
View ArticleBy: Yves
We use another form instead of hours. We are using AP (Arbeitspakete). We break down the whole work into small tasks todo and than burn down those APs. It works fine after some iterations when you know...
View ArticleBy: Stefan Schubert
The funny thing is: The Scrum coaches teach their own deviations each. They told us to estimate functionally not by effort. This way the estimation meeting remains a strategic meeting. The Product...
View ArticleBy: stephan
@Stefan: Ah you! :-) I’d think if you only estimate functionality you need to know what to do (frontend, backend). Even function points are technology dependent (e.g. how many backend systems data goes...
View ArticleBy: Magnus
Hi, dont´t you find it hard to know that you will be ready in time without some kind of estimation of the tasks? I can see a risk that instead of (together with the product owner) take away a story to...
View ArticleBy: Sebastian
@Stefan (the Codemonkeyism one): Are you doing Scrum or Kanban? If you have no review meeting but frequent customer reviews, why should you need iterations? How long are you doing this now? And how old...
View ArticleBy: stephan
@Sebastian: Ah, one from the famous Scrum shops in Berlin :-) “Are you doing Scrum or Kanban?” Scrum. “If you have no review meeting but frequent customer reviews, why should you need iterations?” I do...
View ArticleBy: stephan
@Magnus: “I also think it is strange to take away the review meetings, knowing that you will present your work can prevent you from making a shortcut in a solution.” The review is done after each...
View ArticleBy: Stephane Erbrech
I am a newbie when it comes to Scrum, but I am very interested in all that, and I am currently leading the move to Agile in my company for about 2 weeks now. Nevertheless, I have my opinions about your...
View ArticleBy: stephan
@Stephane: “A sprint is supposed to have a goal, defined by a statement. Something like “All Search feature are finished” for instance.” The sprint goal has been the weakest point in most Scrum...
View ArticleBy: Marcos Silva Pereira
Stephan, It is ok to me skip review for SOME (less valuable) stories and present them while Sprint is running. But, at least as how I think about Review, it is a public meeting, and so, anybody can...
View ArticleBy: stephan
@Marcos: As said before, most companies have a distinct QA phase before release. This is different than acceptance & unit testing. If you do not need a QA phase, good for you. Keep it that way. For...
View ArticleBy: Marcos Silva Pereira
Stephan, I was not talking about drop QA people, but about do QA as an activity that TEAM must do to change a story from “in progress” to “done”. For sure you should have QA activities, but I think...
View ArticleBy: stephan
“In other words, the story is done when all the work – including QA – is done.” If that already works at your company, keep it. Most companies have distinct QA phase and need to transition towards lean.
View ArticleBy: Scrum Software Development Methodology Reading List « Agile Devin
[...] 5 Practices Better to Change in Your Scrum Implementation (codemonkeyism.com) // Comments Off [...]
View ArticleBy: The retrospective session « Scrumnut
[...] 5 Practices Better to Change in Your Scrum Implementation (codemonkeyism.com) [...]
View ArticleBy: Scrum Product Owner
[...] 5 Practices Better to Change in Your Scrum Implementation (codemonkeyism.com) [...]
View ArticleBy: Karen Greaves
I’m not sure I agree with 1. The sprint review is about more than just reviewing the stories for me. It’s also a chance to influence the business priorities for the next sprint. I see it as a crucial...
View Article
