The Scrum Master is responsible for ensuring Scrum is understood and enacted. Scrum Masters do this by ensuring that the Scrum Team adheres to Scrum theory, practices, and rules. The Scrum Master is a servant-leader for the Scrum Team. The Scrum Master helps those outside the Scrum Team understand which of their interactions with the Scrum Team are helpful and which aren’t. The Scrum Master helps everyone change these interactions to maximize the value created by the Scrum Team.
The Agile Culture gap is the nr. 1 cause for immature Agile implementations. You should read this blog if you want to understand how culture affects Agile transformation.
Practically everything we do in life involves negotiation. Many important issues—the political future of nations, the scope of business, the purchase of a house—hinge on negotiation. But negotiation is also an integral part of our everyday lives, whether you are resolving a quarrel, creating a family budget, or simply deciding...
The Biggest Myth in Building a Learning Culture - Learning Rebels
"The millennial generation requires belonging to an organization where a strong learning culture is present." It's common knowledge employees increasingly value a workplace that nurtures learning. Employees want to work in an organization where there is time for self-discovery, time for reflection, debate and thought. They want their potential nurtured, and…
The reality is, everyone – EVERYONE, wants to be part of a business which values knowledge and learning.
Roman Pichler says successful product owners share the characteristics discussed in this post. Are you a successful product owner? Do you have these attributes?
The DevOps Handbook: How to Create World-Class Agility, Reliability, & Security in Technology Organizations eBook : Kim, Gene, Humble, Jez, Debois, Patrick, Willis, John, Forsgren, Nicole: Kindle Store
The DevOps Movement Fits Perfectly with ITSM | Think Tank
Discover how the DevOps movement complements IT Service Management (ITSM) principles and practices in this informative blog post. Read on to learn more.
The Difference between Priority and Order in Your Agile Work
The Scrum Guide talks about an ordered backlog, not a prioritized one. While order and priority are related, they are not the same, and understanding the difference and why people focus on one over the other can help your team be more effective at delivering business value.
The Effective Change Manager's Handbook: Essential Guidance to the Change Management Body of Knowledge - edited by Richard Smith, David King, Ranjit Sidhu, Dan Skelsey), APMG
The Effective Change Manager's Handbook helps practitioners, employers and academics define and practise change management successfully and develop change management maturity within their organization.
The essential guide to agile team working agreements
Learn everything you need to get started with working agreements: the what, the why, best practices, and example templates.
Ask for help when we need itBe transparent and honestActively give constructive feedbackJoin meetings on timeCommunicate our schedule and mark absences to the work calendarOnly work on a maximum of four stories at a time (WIP limit)Link all pull requests to Jira issues
The European Commission publishes first-ever publicly available PM²-Agile Guide
A key extension to the current PM² offering, the new guide incorporates agile values, principles and practices, making PM² applicable to Agile initiatives.
The Field Guide to Understanding 'Human Error': Dekker, Sidney
The Field Guide to Understanding ’Human Error’ will help you understand a new way of dealing with a perceived 'human error' problem in your organization.
In The Phoenix Project, we introduced the Three Ways underpinning DevOps. In my follow-up book, The Unicorn Project, I revisit Parts Unlimited and describe my learnings through the Five Ideals.