ScrumMaster Maturity Model
The intention of this Model is to help organization / individuals to measure and improve the effectiveness of ScrumMasters in their role.
For the Existing ScrumMasters:
- Helps the existing ScrumMasters to evaluate their current position in terms of their role maturity
- Helps the organization by providing the range of maturity level and helps the ScrumMasters to improve in their role maturity
For Agile / Scrum Coaches:
- Helps the ScrumMasters to understand the position where he / she stands and what that really mean by providing the necessary insight
- Helps to find out the action items and coaching technique so that the ScrumMasters can move to the next level of maturity
Expected Business Impact:
- This model can be used in a single Business Unit / across multiple business units as it will be generic.
- This model helps the ScrumMaster community in a single BU or across BU or across product lines to evaluate their position. It provides the path for ScrumMasters to improve and perform their work better
ScrumMaster Maturity Model is developed by Mr. Brian M. Rabon, CST, PMP, President, The Braintrust Consulting Group, USA (http://braintrustgroup.com/). I have started working with him from this year beginning and tried this model as a case study with 8 scrum teams across 3 product groups in my organization (EMC Corporation, Bangalore).
I have the first cut ppt readily available with data's and interpretation.
Outline/Structure of the Case Study
The rough outline of the session:
- Introduction Scrum Framework
- ScrumMaster - Role
- CMMi Model - Just a reference slide - all the top 3 slides for 5 Min
- ScrumMaster Model Hierarchy - 5 Min
- Levels (detail of all the 5 levels) - 15 Min
- Case study & piloting details with data and analysis - 15 Min
- Q & A - 5 Min
- If you have multiple scrum masters working in your organization, this model helps you to find where they stand (in a scale of 1 to 5) in terms of their role expectation & their role maturity.
- This helps the scrum master's to see where they stand and also helps them to grow in their maturity model.
- At the Organization level it helps to define a maturity model and a career path for ScrumMasters
Agile Coaches, Scrum Masters, Process consultants, Head of Engineering, CEO's, VP - HR
schedule Submitted 7 years ago
People who liked this proposal, also liked:
Bernd Schiffer - Net Promoter System for Agile CompaniesBernd SchifferAgile Coach, Trainer, and ConsultantBold Mover
schedule 7 years agoSold Out!
Customer collaboration is essential to every Agile business. To create and collaborate to keep a customer is the purpose of an organisation. But still lots of companies try to make bad profits, i.e. profits earned at the expense of customer relationships. The Net Promoter System (NPS) is a renowned open-source system which addresses and measures customer collaboration. And did you know that you not only can use it to get feedback on your products and services, but also on your employees and your personal performance?
NPS is a perfect fit for Agile companies - and those who want to be. Most of the companies I worked with (Agile coaching, training, consulting) had not heard about it, and far less were actually using it. This really surprises me, since NPS integrates like a charm with Agile, e.g. within product development via Scrum.
In this session I'll explain the basics of NPS, i.e. promoters and detractors, satisfied and delighted customers, bad profits (how to deal with bad feedback?) and good profits, and why and how to measure these. Several stories from companies like Apple Retail, Zappos, Southwest Airlines, and others will help to make my point. I’ll further show why NPS is a very good fit with Agile regarding products, employees, and personal performance. Dos and Don’ts regarding NPS (also from personal experience) will close this session. Related to the Don'ts, I also cover some of the negative critiques out there.
Victoria Schiffer - Agile Coaching? Sure thing! What about Life Coaching in Agile Thinking?Victoria SchifferDelivery ManagerSEEK
schedule 7 years agoSold Out!
I love being around awesome people, who build great products customers desire.
I love learning from and together with these amazing minds.
I love creating the right environment for teams to flourish.
I love change, and learning from new experiences.
I love working in Agile environments.
How about you?
I bet there are some elements of this list why you're in Agile, too. And you can probably add even more elements to it.
The Agile Manifesto states amongst others individuals and interactions, customer collaboration and responding to change.
In our everyday life doing Agile we already respect these aspects in many ways.
But do we practice what we preach as best we can?
I'd like to challenge your current way of thinking about people and processes.
I'd like to challenge you to focus on you, before you focus on others.
I'd like to challenge your current way of reflecting.
I'd like to inspire you to go different ways.
I'd like to inspire you to inspire others.
In Agile we're already good in improving our processes and creating well performing teams and hence building the right things in the right way. And in the Agile Manifesto's communication and collaboration piece we can even get better.
"You have not yet reached the limit of what you're capable of!" means we can always further improve. And we do follow this idea in our Agile processes, too, through continuous feedback (Retrospectives) and improvement.
And why not take it even further? Why not go "Beyond Agile"?!
Here's where aspects of Life Coaching come in handy: through also understanding and improving ourselves (how do we interact with people due to how we perceive our environment) we will even further improve communication and collaboration.
Life Coaches believe our clients know the answer. And even if Agile Coaching is slightly different than Life Coaching, I see it as very relevant in Agile Coaching, too. If we apply this in Agile, instead of giving our clients (team, colleagues) the answers, asking them powerful questions to help them be more aware of what's happening at the moment, they will find their answer for it and will have a much better commitment to making the change for themselves, their teams and the company. It's not for us to TELL them what to do, but to ASK them what's going on for themselves. Here's where I see a huge chance for improvement.
In my session I give lots of examples on how to link Life Coaching ideas to our Agile work environments. I've given the session at LAST Conference Melbourne and at the Agile Coaching Circles Meetup Melbourne. The audience was engaged and the attendees were very happy about having some new ideas on how to improve their daily work life.
Come along to be inspired by Life Coaching and thus to benefit our Agile Thinking!
Giovanni Asproni - Methodology Patterns: a Different Approach to Create a Methodology for Your ProjectGiovanni AsproniConsultantAsprotunity Limited
schedule 7 years agoSold Out!
In the software world we have been looking for “The Methodology” to solve our software development sorrows for quite a while. We started with Waterfall, then Spiral, Evo, RUP and, more recently with XP, Scrum, Kanban, DAD, SAFe (there are many others, but, their impact, so far, has been limited).
In this tutorial, I'll show why this search for the holy grail is bound to fail--each methodology has strenghts and weaknesses that make it suitable only in some contexts--and I'll describe a different approach based on patterns and pattern languages, that teams can use to create their own methodologies to suit their specific needs, which, in my experience, has a higher chance of success.
The approach is based on the observation that all the practices used in all modern methodologies--e.g., user stories, use cases, team self organization, TDD, unit testing, acceptance testing, continuous integration, iterative and incremental development, etc.--come from the same set. Different methodologies just mix and match them differently. All those practices can (and many have already been) described as patterns whose relationships with each other form a set of pattern languages.
Anna Obukhova - The SCRUM and the willpower: how neuroscience can boost your productivityAnna ObukhovaAgile CoachScrumTrek
schedule 7 years agoSold Out!
Willpower is the force that is between the brain activity (I want to do this or I need to do this) and the action itself (start coding). If there is not enough willpower, people find it difficult to start any activity (especially that involves
What is the standard approach when you feel tired and find it difficult to concentrate? Take some coffee (but latest research shows that coffee depletes the brain activity, even when body has more energy), take some sweets (but sugar ends quickly and gives even more exhaustion to the body)? These widely used strategies generally do not work, and in long-term even add harm to the body and brain.
The willpower is not endless (so-called muscle theory of willpower), it can be saved, it can be trained, there are approaches how to keep the willpower level high. To keep the willpower (and thus, productivity) on the high level, people should know and use different approaches that lay in the field on the social and cognitive science.
There are a lot of evidences that SCRUM improves the developer’s productivity in terms of speed of development, code quality, and accuracy of design. Unfortunately mainly all recommendations from SCRUM coaches look like “believe me, if you do this, you will have better velocity”. Yes, it works. But why does it work?
Sometimes SCRUM does not give such great results even when main elements are in place. The question “Why” and “What makes the difference” is here again.
I will describe the model of relationship between the willpower related brain metabolism on very low level (specific amino acid cycle) and the SCRUM practices. I can prove that SCRUM addresses the productivity of the people’s brain using 3 different flows simultaneously. There are several tips that make these productivity flows working or not. You can make Agile productive, you can have non-productive Agile. I will show you where the difference is.
Overall there are 10 productivity tips that can be put into 3 flows.
As the outcome of this session, Agile coaches, and all people who can change the process (in fact that is any team member) will review their SCRUM: does the way they have it improve the productivity or they are losing all the power? The changes are cheap, the outcome can be huge.
Tushar Somaiya - Why Scrum Works? - A NeuroScience PerspectiveTushar SomaiyaFounder, Director ShuHaRiAgileShuHaRiAgile
schedule 8 years agoSold Out!
Have you ever thought why scrum works? That too from NeuroScience perspective?
We all acknowledge and understand that we have moved beyond and past machine age or service era and are living in what is called “Knowledge Era”. Focus of current times is shifting from behaviours to values. From people to brain. Yet, we know very little about people or brain or its working.
Through this talk, I will attempt to link hard neuroscience to scrum and its practices to see why it works or does not work. Also we would look at practices required beyond scrum to create an environment where scrum can flourish. Or even exists!