Approval or feedback in the Sprint Review?

The Sprint Review meeting begins. The Development Team and the Product Owner show the client what they did during that Sprint. The client observes, but doesn't say much, except for a few basic questions. At the end, the client approves (and even applauds) the work, says good-bye and leaves. Everyone thinks, "Phew! The meeting was [...]

By | 2017-11-22T16:19:14+00:00 April 7th, 2017|Planning|1 Comment

Automated tests? Where do I start?

Today’s text intends to explore a question that we sometimes hear from clients. It’s common to hear things like: “Now I understand the importance of having automated tests! The tests which are 100% manual are sacrificing our time and the quality of the release. But where do we start? What types of tests should we [...]

By | 2017-11-23T09:46:40+00:00 April 5th, 2017|Automated Tests, Developer, Scrum|0 Comments

Product Backlog, Continuous Planning and the Horizon Analogy

Imagine this scenario: you're out in the street watching the city in front of you. Buildings, cars, people and other things are distributed from where you are standing to the distant horizon. To describe what you see, what level of detail can you use in your description? Now imagine your next software development project. When you [...]

By | 2017-11-23T12:34:34+00:00 March 31st, 2017|Planning|0 Comments

Controversy: The Best Product Owner Is Not the Client

The Product Owner (PO) is certainly the most neglected of the three Scrum roles. Precisely for this reason, many organizations end up finding a solution that seems to be easier than training or hiring a good PO: giving that title to the client. Because of that, we often hear the notion that the best Product [...]

By | 2017-11-23T13:10:41+00:00 March 29th, 2017|Product Owner, Scrum|0 Comments

“New System Version!”

Almost everyone who works with computing, or at least works closely with an IT team, has heard this sentence: “We have to rebuild the system!” The result is a new system version released frequently. There can be many reasons: Replacing outdated technology A new platform Or the most genuine reason: providing maintenance to the code [...]

By | 2017-11-08T12:30:45+00:00 March 22nd, 2017|Developer, Scrum|0 Comments