Book Summary - Scrum: The Art Of Doing Twice The Work In Half The Time
My key takeaways:
- Scrum needs involvement and alignment from all stakeholders to bring value to the project as early as possible
- Scrum is based on the people they work with; and also it completely varies between the pods and scrum teams
- Clearly define the roles of the team, Scrum Master, Product Manager, Product Owner, Development team along with the QA, etc
- Product development also follows the Pareto Principle: 20% of the requirements represent 80% of the product's value. Thus, the objective is to prioritize the items for the current sprint
- MVP and delivering smaller chunks of product backlog without no major risk to the current production capabilities is the success of scrum
- PDCA cycle (Plan, Do, Check and Act)
- Have a clear way of defining DoR (Definition of Ready) and DoD (Definition of Done) for your scrum team
- Follow your suited sprint ceremonies to get the most out of your scrum outcomes, such as Sprint planning, Sprint, Daily scrum meeting, Sprint Review, and Sprint retrospective
- How fast the daily raised impediments during the scrum standup are getting resolved would define the agility of your scrum team
- Make sure to provide a clear vision, and refine the product backlog so that the sprint backlog is very clear to the scrum team
Reference:
http://amazon.com/Scrum-Doing-Twice-Work-Half/dp/038534645X
No comments:
Post a Comment