Live Draft: Agile Project Management: Lessons Learned at Google and some new Scrum things to try out : Jeff Sutherland (QCon)
- Projects are late, developers are blamed!
- scrum is to release people from their chains!
- Scrum is based on one of japaneese best practices (Toyota)
- We place the highest value on actual implementation and taking action.
- There are many things one doesnt understand th therefore, we ask them why dont you just go and do them.
- Developers Start to feel responsible
- Dicipline should be brought by creative leadership…
- Weekly meeting of all stakeholders
- Companies like to “start light”, by choosing features from a methodolgy! Then they blame it for any fail.
- Behind the ABC of scrum there are certain needs such like collaboration,
- google in its evoleving towards agility observed what problems they got
- got problems with deadlines: Introduce a Release BurndownChart
- got problems with testability because of dependency with other developers work : they used Scrum daily meetings
- Google then failed on delivering on date
- Introducing full Scrum implementation
- Product/Release Backlog
- Iteration Based Development (2 weeks iteration)
- Testing tasks for iteration’s feature s in the same Iteration
- Sprint Burndown to guide actual development efforts
- Release Burndown to guide the overall release planning
Practices: Transperancy >> Daily scrum taskboard
Scrum of scrums for communication teams
The scrum check list
When Scrum is will implemented by a good scrum leader, Scrum starts running itself.
Customer Responsibilities Board designed for assuring that customers dont get 50% of their needs, thats a 100% project failure!
Scrum makes presonal team individuals presonal problems as important as tachtical problems , up on the top, for improving communication and productivity.
Scrum introduces something like a viruse that activates the communication and productivity cycle.
Scrum is introducing a management roles that responsible to make a strategy that works… it was suggested by CMMI and introduced by Jeff Sutherland and Ken Schwaber and reviewed by Scrum Alliance.
I like the slide “You know you don’t do… when”. I’ll reuse it!
Comment by Eric — March 16, 2007 @ 9:42 am
me too
Comment by sadek — March 16, 2007 @ 3:16 pm