The difference between Scrum and Integrity
We have been using Scrum here at Typemock and it has really
helped with our software development, but we also manage with integrity. There are a few major differences between the two styles.
Roles.
In Scrum there are many defined roles, where some are seen as more committed then others.
In Integrity there are no defined roles, everyone is committed.
Meetings
Scrum, there are set meetings.
One daily meeting
- What have you done?
- what are you planning to do?
- Do you have problems?
Three Monthly (Sprint) meetings
Sprint – Select the work that must be done.
Review – Demo
Retrospect – How can we improve
Integrity, There are set meetings
Morning Meeting:
- What can the team commit to doing today?
Evening Meeting:
– Keep Integrity (tell others if not)
– Raise and Solve problems, Praise
Weekly Meeting:
– Was last week with integrity?
– What can the team commit to doing this week?
– Raise and Solve problems, Praise
Change Monthly goals once a month.
Artifacts
Scrum: Burn Down, Sprint Backlogs, Product Backlog
Integrity: goals and controllable actions
Main difference: Transparency
While Scrum put a lot of focus on the structure of the development process and team, and allow rapid development and addresses the chaos typically found in complex fast moving environment, Integrity focuses on personal growth and team work.
The big difference in my view is that with scrum it is too easy to say to the customer at the END on the sprint:
”Sorry, Mr. Custromer, we just didn’t make it on time, we will but it on our backlog” – Ahhhhh
So if the management has a goal: Close Sale with Customer [put huge customer], and to do this the R&D must implement the ABC feature. We might reach the end of the month without that feature being implemented and management won’t know about it.
With Integrity, this will never happen. If after 5 days the team knows that he is not able to keep up with the controllable actions that where defined to reach that goal, the team must tell management about the delay in order to be with integrity.
Now that the management knows about the problem, we can solve it.
- By asking the team what it needs to solve the problem in time.
- By moving resources
- By changing priorities
- By telling the customer about the delay
The last bullet: telling the customer about the delay, is the highest point of integrity, and the customer will appreciate the knowledge and know where he stands.
Management with Integrity will not only help put structure in the chaos of complex fast moving environments it also focuses on personal growth and excellence, on solving challenges and not only managing them.
Recent Posts
- Unacceptable: Unit testing will take 20 years to catch on
- The 4 reasons why we DIDN’T choose Oslo
- Typemock Academy Launch
- The First Rule to Software Craftsmanship
- Goal-driven Development
Categories
- .NET Tests
- Agile
- Code Integrity
- Community
- Debugging
- Fun
- Management for Geeks
- Marketing
- Product
- Release
- Reviews
- SharePoint
- TDD
- Time Management
- Uncategorized
- Unit Tests
Archives
- May 2010
- April 2010
- March 2010
- February 2010
- December 2009
- October 2009
- September 2009
- August 2009
- July 2009
- June 2009
- May 2009
- April 2009
- March 2009
- February 2009
- December 2008
- November 2008
- August 2008
- July 2008
- May 2008
- April 2008
- February 2008
- January 2008
- December 2007
- November 2007
- October 2007
- September 2007
- August 2007
- July 2007
- June 2007
- May 2007
- April 2007
- March 2007
- February 2007
- January 2007
- December 2006
- November 2006
- October 2006
- September 2006
