When you come to a Scrum or Agile conference, you pick up new ideas that you’d like to try when you get back to work. However, you may feel like you hit a brick wall when it comes persuading your team to try the idea out. Resistance is very common in organisations large and small.
In Scrum, the velocity is defined as amount of work that the team can handle in one sprint. This is an important measure as it is used to plan the future iterations and to verify that the team is progressing at a constant and comfortable pace. In this blog post, Agile coach Rachel Davies presents a FAQ on how to calculate velocity.
The role of the coaches and ScrumMaster is to give feedback to the members of the Scrum teams. In this article, Francesco Attanasio proposes a model based around the FEELING acronym: Facts; Emotions; Encouragement; Learning; Implications; New Goals.
Do you know situations where the team spirit and/or quality of results were decreasing? This might have been complex situations and maybe it took a lot of time to fix it. But did it change on a long term? I suggest an easy to use way with all team members to get and stay in a continuous improvement loop.
This presentation will help you understand what it takes to run a successful agile release planning meeting. The release planning is the “pacemaker” of enterprise agility and the Agile Release Train (ART) which aligns the Agile program to a common mission. Based on nearly a decade of experience, Dean Leffingwell and Scaled Agile have developed a process which has worked with small trains of 40 people to larger trains of 180. This video explains what it takes to run a successful Agile release planning meeting from a scaled point of view (100′s of teams).