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 in a DevOps way.
Continue reading “What is really DevOps?”
When comparing the frequency and granularity of test planning and execution in products developed under Waterfall and Agile methods, we observed that in Agile: we have more tests, in the story level and we have a progressive increment of test coverage all over the product and higher frequency running those tests.
Continue reading “Why Agile test planning makes software quality superior than in Waterfall”
Life is done of routines. A routine has a taste of contradiction: sometimes is boring sometimes means comfort, security, trust. Respect a routine implies discipline and recognition about the value we can get from that. In this post I would like to share my thoughts about the Continuous Improvement cycle. I think this is a basic concept you must understand once we enter in Agile and specially if we start planning to adopt a DevOps model to guide our development. Let’s pay attention to this positive loop.
Continue reading “The Continuous Improvement Cycle”
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.Continue reading “Why should we estimate?”
(Somewhere in the EU Sky) Normally when an Agile Transformation starts, it starts by the bottom of the structure. It’s easy to get Scrum up and running in small Agile Teams.
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.
Continue reading “The importance of the regular alignment between different Organization levels”
(Königssee, Germany) Facing an Agile transformation process, it is extremely important to bring together a team at the same level of “language” and knowledge about the Agile methodology.Continue reading “Bringing a team together during Agile Transformation”
I’m very happy to announce today our first Interview with Agile professionals!
I invited Mark Ansonia for our first interview with experts in Agile roles. Mark is a very experienced Scrum Master and Agile Coach, in this short interview he will share his experience among different projects and industries.
Continue reading “Interviewing Agile Professionals: Mark Ansonia”
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.
Continue reading “What is a Team? What makes a Team?”
Agile Transformation is a test for the executives capacity to drive organizational change and business competitiveness. Agile Transformation affects all management levels and areas in the organization: since Tools, Processes, Structures and Resources individually. It’s really tough for managers to impose so many changes at once and keep the business running competitive and innovative. A huge challenge I would say.
Continue reading “Agile Transformation is a test for executives courage”