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 is a change in The 2020 Scrum Guide that I really like. It's the one related to a definition of a Scrum Team.
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.
One of the software engineering manager’s responsibilities is to understand the team’s dynamics and to know if your direct reports are happy in their jobs. While it sounds easy getting full insights from 1:1s, team meetings, or from your direct collaboration with the team is not always that straightforward. It may happen that your team members wait with raising their concerns or...
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...
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.
At some point in time, many Agile teams struggle with how to handle bugs and/or maintenance tasks they are faced with. And the core of this problem is whether bugs should be estimated or not. As always, each approach has its pros and cons, but based on my experience I reckon that estimating bugs is not worth the hassle. Let me explain why.
Early this year Harvard Business Review published an interesting article about innovative organizations by Gary P. Pisano. Most organizations perceive innovative culture as a key to their future competitive advantage and therefore something leaders want to establish and invest in. Also, employees value innovative organizations and consider them as a great place to work for. Moreover, it seems...
One of the most common complaints you may hear about Scrum is that it introduces too many meetings. Let’s have a closer look at this problem. Summary of Scrum meetings Scrum framework defines several meetings that are designed to address 3 pillars of every implementation of empirical process control: transparency, inspection, and adaptation. All Scrum meetings are time-boxed and for a 2...