... you will never turn back
There are many definitions for DevOps, the most simple one can be a unique team able to develop and to operate in a continuous way, supported by a tool chain enabling automatically code integration, test and deployment in a single pipeline, where the code, after several approval steps, is released into production. In this post, I will try to share my definition and will share some personal considerations about the implications of decide for organize your team and development process
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.
When Agile Transformation enters in a scale process, the challenge starts. It is mandatory regular alignment across the different portfolio levels to make sure that the Transformation occurs.