When we talk about longer-term planning in Agile world we usually focus on estimating (i.e. in Story Points), team’s velocity and a way of forecasting a timeframe by which a predefined set of backlog items can be delivered. While the above is absolutely valid and critical, we often forget that a success of a long-term delivery also depends on how a product backlog for the is prepared and...
Inverse Conway Maneuver
How to use Conway's Law to your advantage.
The 2020 Scrum Guide – Product Goal
In The 2020 Scrum Guide a new concept - Product Goal - was introduced. The Product Goal describes a future state of the product which can serve as a target for the Scrum Team to plan against. It basically serves as a long-term objective for a Scrum Team to achieve.
The 2020 Scrum Guide – definition of a Scrum Team
The is a change in The 2020 Scrum Guide that I really like. It's the one related to a definition of a Scrum Team.
The 2020 Scrum Guide – is a potentially releasable increment not needed anymore?
In November 2020 a new version of the Scrum Guide was published. The summary of changes can be found here and in a series of next few posts I will try to share my thought on some of these changes. However, there is one change that is not listed there and that, in my opinion, is quite significant. Potentially shippable increment is gone Have you noticed that there is no reference to a...
I am often asked about books I recommend that aspiring leaders should read. Appearances to the contrary, it is not an easy question to answer. I went through what I recall I have read and came up with the following, very narrowed-down list of books I think are mandatory for every software engineering manager.
In a perfect world, a Scrum team should be allowed to execute their sprint without being interrupted, and all changes or new requirements should be addressed at dedicated Scrum events. While Scrum teams should aim for a world of no sprint interruptions, it's not the reality most teams face on daily basis. Customer usually do request new functionalities, users do discover critical defects, etc...
Definition of Ready
Most (if not all) Scrum teams have a more or less formal Definition of Done (DoD) that dictates when a given user story can be considered as completed (done) and ready for shipment. At the same time, only a few Agile teams have a Definition of Ready (DoR) which, if used smartly, can also give the team a lot of benefits and prevent them from wasting their precious time.
Confessions of a Change Agent (by Henrik Kniberg)
Recently I’ve come across a presentation “Confessions of a Change Agent” done by Henrik Kniberg at Agile Rock Conference 2018. Highly recommended for everyone who is or wants to be an internal or external consultant helping organizations to improve (well, change). The main points: Attitude not a roleChange is easy if people want itInspire > ChangeSlow down to speed upPlant...
Limiting WiP is easy, isn’t it?
Today I came across the following article by John Cutler.
Great summary of why limiting WiP is not that simple and involves many changes to the organization itself.