We evolved our process organically, from Lean, to something close to Shape Up
We defined problems that needed to be solved, and gave them to the team to solve. But we didn’t use cycles or any time boundary
We simple defined what was the most important problem to solve and worked on it until it was acceptable to move to the next thing
This works well when you have a small team, so no more than two iniciativas can be underway concurrently
Full Shape Up would be better when you have multiple teams, and more options for what to work on, so you can make better informed decisions about priority (betting)
sounds interesting! thanks for sharing it, without any time boundary isn’t it tricky to have smth released? How the team knows what solutions to design and how much to invest in that?
We start with a Problem Definition. We then work together as a team on a Solution Design. In that stage we discover how much work might be required to "completely" solve the problem. Then we decide how much we want to work on at that point in time, and we set off to do a good job at it.
Is not like a blank check where you get to go down rabbit wholes or things like that. Is more like we don't want to handicap the solution on predefined time boundaries.
If when we are working on a solution we discover things that change our assumptions, we can re-evaluate and decide what to do about it.
We evolved our process organically, from Lean, to something close to Shape Up
We defined problems that needed to be solved, and gave them to the team to solve. But we didn’t use cycles or any time boundary
We simple defined what was the most important problem to solve and worked on it until it was acceptable to move to the next thing
This works well when you have a small team, so no more than two iniciativas can be underway concurrently
Full Shape Up would be better when you have multiple teams, and more options for what to work on, so you can make better informed decisions about priority (betting)
sounds interesting! thanks for sharing it, without any time boundary isn’t it tricky to have smth released? How the team knows what solutions to design and how much to invest in that?
We start with a Problem Definition. We then work together as a team on a Solution Design. In that stage we discover how much work might be required to "completely" solve the problem. Then we decide how much we want to work on at that point in time, and we set off to do a good job at it.
Is not like a blank check where you get to go down rabbit wholes or things like that. Is more like we don't want to handicap the solution on predefined time boundaries.
If when we are working on a solution we discover things that change our assumptions, we can re-evaluate and decide what to do about it.
ah I see now why this would work best with real small teams, thanks for sharing!