What is your take on the Retrospective: A routine exercise at the end of a Sprint, supported by standard operating procedures? Or a critical part of a Scrum team’s journey of continuous improvement? As you may assume, I advocate for the latter. In my experience, Scrum teams start utilizing Retrospectives to their full potential when they embrace a short set of Retrospective first principles, outlining the essence of the Why, the What, and the How.
TL; DR: Product Backlog Refinement First Principles
The Product Backlog refinement is a continuous process to create actionable Product Backlogs, enabling a Scrum Team to run Sprint Plannings at a moment’s notice. Consequently, refinement is about creating alignment among all team members about the Why, the What, the How, and probably even the Who regarding the upcoming work for the Scrum team’s Product Goal. As a result, Product Backlog refinement is a critical success factor as it drastically increases the team’s capability to deliver valuable Increments regularly.
The following 14 first principles describe in broad strokes the foundation of a successful approach to refinement.
Given the importance of a viable Definition of Done for a Scrum team’s success, it has always puzzled me how complacent or ignorant many Scrum teams are regarding their Definition of Done. So, let me share with you the ten first principles of this critical Scrum success factor to improve your team’s effectiveness, team spirit, and reputation.
Trust is the beginning of everything. I am hesitant to recycle an old slogan of a banking institute. However, in the context of becoming a learning organization and embracing business agility, it condenses the main challenge perfectly: How shall we convince the incumbents with vested interests in the status quo to give the new way of working the benefit of the doubt? Join me and delve into how distrust manifests and what we can do to earn stakeholder trust.
TL; DR: Increasing the Velocity of Value w/ Dave West — ACB21
In this highly engaging speaker session from the Agile Camp Berlin 2021, Dave West talks about why orienting to value rather than work is a crucial requirement for building an agile capability: Velocity of Value.
Contrary to popular belief, the Scrum Master success principles are tangible, when we guide the analysis with an outside perspective.
Read on and discover four Scrum Master success principles: From when not to use Scrum to product quality to supporting the Product Owner to putting self-management at the center.
This website uses cookies so that we can provide you with the best user experience possible. Cookie information is stored in your browser and performs functions such as recognising you when you return to our website and helping our team to understand which sections of the website you find most interesting and useful.
Strictly Necessary Cookies
Strictly Necessary Cookie should be enabled at all times so that we can save your preferences for cookie settings.
3rd Party Cookies
This website uses Google Analytics to collect anonymous information such as the number of visitors to the site, and the most popular pages.
Keeping this cookie enabled helps us to improve our website.
Please enable Strictly Necessary Cookies first so that we can save your preferences!
