... you will never turn back
Why should we estimate? What are we considering when we do it? Yes, estimation accuracy is a matter of practice maintaining the same team constant. What and how can we estimate? We can do it all over hierarchy of requirements, since strategic levels until implementation ones. But essentially a good product planning should be done to slicing features maintaining product value and introducing complexity across the product development phases.
We can explore those questions from different angles, but my simplified definition is: a team is a group of individuals moved by a common goal. Everything is better if, in the meantime we move together towards the goal, we share a positive energy and attitude in between the group.
(Berlin, Germany) Sometimes the most obvious Agile concepts are not so easy to be applied when we need to make a practical usage of them. Specially if we need to bring into a consistent and common understanding a product or portfolio vision for later implementation. My goal with this post is to share a very personal opinion about how and whom should fulfill those Agile requirements levels.
A backlog is such an important asset for each Agile Team and even more important for a company who understands the value to demand for high quality content and well organized backlogs. What I would like to share with you today is a set learnings I did since I’m working in Agile.