Category Archives: Agile

In the Agile category you will found information about agile methodologies like Scrum or Kanban for product teams, development teams or business teams. Also will be published content and information about Backlog management, Scrumban, Lean Startup, Visual Management, etc.

Scrum Master certification comparison. Which should I choose?

Since I started working with Agile some years ago, there are tons of doubts that people ask me in my work with different clients, in community meetings or at my day to day, but there is a question that lately many people repeat me, and that seems like its more difficult every day for not initiated people: Which is the best Scrum Master certification program?

Given the explosion that we live in recent years with everything related to agile methodologies, and not only at the level of software development in small niche companies or start-ups, but also at large organizations, it is not casual the appearance of many companies willing to be providers of Scrum Master certifications. Companies that do not necessarily have a long career in the Agile world, and that are not backed by recognized entities, but who have created new certification programs that have flashy names, difficult to distinguish, and all of them written as three-letter acronyms, which makes it certainly difficult to differentiate between them.

Scrum - Scrum Master certification

Is quite easy for the people who is involved in the community to identify the most recognized certifications, but it is not a simple task for those who just arrived to the Agile world. And although there is no a direct answer for the question of which certification is better, as this depends of the preferences and possibilities of each person, it is true that exists certain information that can be analyzed to take the best decision for each personal situation.
Continue reading

Share:
Share on FacebookShare on Google+Tweet about this on TwitterShare on LinkedInBuffer this page

Agile Retrospective (with Retromat)

During the agile retrospective, also known as retro, the team reflects on what happened in the iteration and identify actions to focus on the continuous improvement.

In those meetings, identified as one of the ceremonies of Scrum framework, and timeboxed to three hours or less, the team reflects about the daily work of the team itself, both qualitative and quantitative way, endeavoring to uncover what is working well, what isn’t, and what can the team do better the next time.

Retrospective

The quantitative side of the agile retrospective is relatively easy to address and understand, provided that we have access to data about work and team performance. Metrics about team velocity, value delivered, defects density or even data about team’ happiness are really relevant in every day life of a good agile teams, and may provide clues to proposing improvement actions. Having a history of all the data that as a team we consider relevant we can do comparisons and identify trends and breaking points that have affected productivity, and we will obtain conclusions about what has been happening in the team over the time.

Thus, the quantitative side of an Agile retrospective seems a simple task, but it is not the case of the qualitative side…
Continue reading

Share:
Share on FacebookShare on Google+Tweet about this on TwitterShare on LinkedInBuffer this page