Can Velocity be an indicator of a Scrum Team's Maturity?
First things first, why "Velocity" alone, when there are many other factors (requirements, estimations, defects, automation etc) which would help arrive at a Team's maturity? So, with so many other factors in the ambit, why does this session emphasizes on "Velocity" alone, while I could have just easily entitled this session as "Various factors influencing a Team's Maturity"?
Let me start with the statement that "The more the velocity, the more the more productive the team is and hence more matured". It sounds fairly correct right? A team with more velocity is more likely capable and productive and hence more matured. Isn't it?
But wait, consider this!
> What if the team has shown significant "progress" in increasing their velocity but at the cost of team's burnout?
> What if the team has increased their average velocity by X percent but has compromised their quality?
> What if the team has padded their product backlog with the list of stories which are more of "non-functional" in nature which don't necessarily add any business value?
> What if the team has "bloated" their velocity unusually by sometimes(or many-a-time probably) by projecting simple tasks as stories-with-a-business-value?
Can the team be branded a matured?
And the reason as to why the team resort to such anti-patters to "save their velocity" is because "Velocity" which is ought to be the primary measure of a Team's progress, has metamorphosed into a "performance metric" leading to the teams (their leadership hierarchy too) becoming conscious or (rather "obsessed" in many cases) with Velocity so much so, that in order to "preserve" or "increase" their velocity, teams can resort to anti-practices such as extending the sprints, bloating the story points, add stories that don't add value only to "maintain" velocity.
Having said that, while its true that Velocity is certainly a critical indicator to measure of the amount of work a Team can accomplish in a sprint, it should also be seen in the context of the team's ability to maintain a consistency in achieving the velocity and at the same time, take a closer look at the team's definition of velocity itself.
Notwithstanding the above points and considering that a team gets them all right, can we then say that Velocity drives a team's maturity? To an extent, Yes. Velocity can be an indicator of a Team's Maturity but it cannot be the ONLY factor determining it. Among other factors, Maturity can also encompass how effectively the team tackles the dimensions such as "planning", "quality", "practices", "communication and collaboration" etc. (the list is exhaustive).
It is in this context that this session aims to throw some light on what "Maturity" and how "True Velocity" can contribute to a Team's maturity and discuss about numerous other factors that contribute to a team's maturity, such as a team's ability to break the silos and "self-organize" themselves, adhere to "practices", learn to cultivate "mutual Trust", "team commitment","collective ownership" and many more.
Outline/Structure of the Presentation
This session is not to promote/advocate or figure out a "Maturity Model" for a team.
More than a presentation, this will be more of an interactive session where the attendees/participants will indulge in meaningful discussions, and debate about their take on "Velocity" and "Maturity" and how they can influence/complement each other on the team's journey towards Maturity.
During the first 15 minutes of the session, the speaker will try to reiterate the premise of what Velocity and Maturity are, discuss about what it means to the audience and get their perspective on them.
The next 15 minutes will focus on the intricacies of how Velocity where questions/factors related to Velocity will be discussed in detail.
The next 15 minutes will try to establish the relation between Velocity and Maturity and take a deep dive and discuss/debate on how they are complementary/contradictory to each other and also discuss about the challenges we usually face in this area.
The last 15 minutes of the session will be for any Q&A and try to address them accordingly. Power point slides will be sparsely (or not at all) used as most of the session is more interactive than a presentation.
> Understand about the anti-patterns centered around velocity calculation and its misuse.
> Understand what Maturity stands for and what does it mean to the Agile/Scrum teams.
> Understand how Velocity and Maturity are complementary/contradictory to each other.
Scrum Masters, Product Owners, Scrum Team members, Project/Product Managers, Stakeholders
Prerequisites for Attendees
Attendees should have:
> A basic working knowledge of Agile/Scrum.
> The definition of Velocity and how Velocity is arrived at.
> How estimation is done in Agile/Scrum teams.
schedule Submitted 8 months ago
People who liked this proposal, also liked:
Satya Jyoti Yellapantula - Smart way of choosing Retrospective TechniqueSatya Jyoti YellapantulaScrum MasterPegasystems
schedule 10 months agoSold Out!
There are many retrospective techniques available and its a widely discussed topic too. But every sprint and release is different with respect to outcomes and learnings. The Scrum Master need to have the expertise to chose what technique or Agile game for Retrospective event so that it opens up healthy discussion and best learnings from the time boxed event. Example, Speed Boat is a great Retrospective technique, but may not be the best during the first or second sprint. Similarly, in case of release retrospective, where relatively large number of audience are present, there are multiple things to consider while chosing the format of Retrospective, like do you have a distributed audience, the number of audience, to what extent was their work co-ordination needed during the release, etc.
Hence, chosing the right Retrospective Technique is an art, and in this session we will discuss practical situations and what retrospective technique works best in those situations. I will discuss the tried and proven techniques based on my experience. I will share what retrospective technique worked when the team was newly formed, when the Scrum Master was new to an old team, when the team was continuously unable to meet sprint commitment, and a few practical ways of effectively facilitating the event for large audience.
Sivakanth - Being a Scrum Master ain't an "extended" responsibility. It's a role in itself.SivakanthScrum Master Level 2Pegasystems Worldwide
schedule 8 months agoSold Out!
The Scrum Master is responsible for promoting and supporting Scrum as defined in the Scrum Guide.
As defined in the Scrum Guide, the role of a Scrum Master is responsible for promoting and supporting Scrum, by helping everyone understand Scrum theory, practices, rules, and values.
But in practice, we often see this important role as an "extended" role, an "additional" responsibility, usually played by project managers or any of the senior member of the team who is expected to "make things work". This role is often pushed into a dilemma between the "expectations" (to solve every other problem that the team faces) and "reality" (to take a step back and let the team get empowered to solve their own problems).
While the role includes facilitating a conducive work environment for the Scrum Team, guiding and teaching Scrum practices to everyone involved in the project and clearing impediments for the team, it also includes facing resistence from the teams, management, stakeholders and sometimes, probably of all them put together. The challenges could vary from "Time-boxing the Daily Scrum Meeting to 15 minutes" to "the extent of owing the team's deliverables on a whole".
This session aims to take a realistic look at the usual challenges (and probably any unusual ones too) that the Scrum Masters face and try to understand some best practices centered around this role as an outcome of the discussion.