Great article by David about how “lean” Scrum is or can be.
Inspect the inherent Lean qualities of the Scrum framework along with various ways to help Scrum Teams improve using Lean Thinking.
Full article
http://msdn.microsoft.com/en-us/library/jj161049.aspx
Q: Why do we need a Sprint Burndown or BurnUp in the 1st place?
A: Some teams use it to monitor the progress towards the Sprint Goal.
Another good approach is to use a physical board where you can see the progress very easily!
I had a discussion a while ago about what do we burn on the burndown chart:
The problems with burning “time for tasks”:
Three bad examples of user stories:
“As a developer, I want to integrate with other system in an IntegrationEnvironment, So that I can test the Integration”
“As a project team, we want to setup SharePoint, So that we can share documents”
“As a developer we want TFS as a build server, so that we can build code automatically”
I experienced lots of projects where we had those and those are a huge problem! They go in the same direction as the smell of having a “Sprint 0”
Nice article about Scrum -> MUST READ if you are into Scrum
Nice article from fellow Scrum Trainer about the differences between “Scrum” and the “Kanban Method”
Make sure to understand the difference between “Kanban” and “The Kanban Method”
Full article
http://scrumcrazy.wordpress.com/2013/02/04/kanban-vs-scrum-kanban-is-not-for-software-development-but-scrum-is/
Great article that describes common obstacles to agility in large organizations.
Article in PDF Format
http://scrumreferencecard.com/Obstacles_To_Enterprise_Agility_255033.pdf
Nice article about
From experience, I know it takes a certain amount of time to add one brick to a wall. Adding additional bricks will take about the same amount of time. Therefore, I can give you a somewhat accurate prediction of how long it will take to build an entire wall.
Writing software, like Finding a Cure for Cancer, is more a research activity
3 concepts from Scrum which can help solve this problem of estimation:
1. Estimate using Story Points
Story Points are not part of Scrum, but anyway a good abstraction from time.
The biggest advantage is that they force you to estimate relatively!
[Advertisement] Come to my class to see this in action ;-)
2. Work in Sprints
3. Break Stories into Tasks
…management cannot accurately estimate the business value of a project until a project begins
This requires trust and a couple of Sprints to get a feeling on how the Dev Team is going
Demanding that a developer provide a time estimate forces the developer to lie and no one likes to lie.
In addition, every developer follows the Parkinson’s Law
”Work expands so as to fill the time available for its completion.”
Full article
http://www.scrumexpert.com/knowledge/why-you-should-not-estimate-in-hours-or-days/
The Scrum Developer Open assessment is a tool for validating your basic knowledge of the software development tools and practices that can be used within the Scrum framework.
30 questions in 30 minutes
PSD Open Assessment *
Start here
http://www.scrum.org/Assessments/Open-Assessments/Developer-Open-Assessment
* PSD = Professional Scrum Developer
Open = Free
Great post from Henrik that highlights the nature of the Scrum events.
Nice saying
In popularity, “meetings” tend to be viewed as enjoyable as a dentist appointment.
Best bit
These are not meetings though. These are working sessions where each individual is fully focused on the collective task, participates every minute by learning or contributing and leaves feeling energized from new insights and happy from all the progress that was made in such a short time.
Some tips on how to improve your “meetings”:
How to improve your Meetings?
http://gfader.tumblr.com/post/27114162908/how-to-improve-your-meetings
Full article
http://www.cedur.se/agile-blog/2012/10/there-are-no-meetings-in-scrum/
Gunther has some great visualizations of ”Lean” and “Scrum”.
He calls it the “The House of Scrum”: Standing on “Transparency” and 2 pillars: “Inspection” and “Adaptation” with the goal of the “Product”.
The House of Scrum is a great and energizing place where product development prospers from the combined, creative intelligence of people.
Who would not like to work there?
I really like the way how Gunther shows the compatibility between “Lean” and “Agile”
Lean —- Agile
Full article
http://ullizee.wordpress.com/2011/10/22/the-house-of-scrum/
Learn how the cadence of Scrum and Continuous Delivery can help you build the right thing, and when implemented properly, release it on time to ultimately deliver superior value to your customers.
Nice article from fellow trainer Ryan.
Great tips (short form here)
Do:
My tip:
Instead of the 3 questions focus on the top 1 Backlog item.
How can we complete the 1 most important Backlog Item to “Done”?
Full article
Daily Scrum: Attack the Day
http://blog.appliedis.com/2012/10/09/daily-scrum-attack-the-day/
Sentinel is “arguably the most important application at the FBI,” and agile development turned out to be the right way to complete it, Fulgham told me this week.
Full article
http://m.iwgov.com/264939/show/d46f562ca736be435abad7fc5e595bc3/
Process has been much maligned by the Agile community, beginning with the Agile Manifesto line: (We Value) Individuals and Interactions over Processes and Tools. Not that this is altogether a bad thing. At the time the manifesto was created it was the individuals and interactions that were maligned, and this was a way to right the balance. But if process is thought of simply as “what we do” then process itself can be a force for change.
My favourite part:
We can’t convince people of Scrum through presentations, case studies, or other “evidence”. People need to experience Scrum to truly understand it. Many won’t even start.
Well said!
Great quote that highlights a delusion with Agile/Scrum
Put some high-school students in a hospital operating room and say: “OK, self-organize and perform brain surgery on this patient!”
Full article
Scrum, Skill and Dead Bodies
http://blog.chadalbrecht.com/post/2011/12/13/Scrum-Skill-and-Dead-Bodies.aspx
RSS feed