Agile - An era of "Asking" (with insights from a survey)
One of the prime goals of successful Agile transformation is creating self-organised teams. Teams become more self-organised by simply questioning Who will do What, Why, How and by When? While this sounds simple, just like Agile transformation, it is not easy. With small steps, incrementally, we can improve Team's asking skills.
This presentation highlights the importance of "Asking" and lays its foundation on a survey, which I conducted recently. The results of the survey clearly show that teams, which did more asking, have witnessed effective value delivery more often. In the process, the presentation also introduces two new measures called "Team asking quotient" and "Value Delivery quotient" which is derived from 7 important areas that determine the overall asking maturity of a team.
Outline/Structure of the Presentation
1) Benefits of asking by introducing an acronym called REWARD : 3 Minutes
Asking has many benefits like Building Relations, Empowering people, Eliminating waste, Finding better alternatives, making reliable decisions or discovering something more interesting. In this sub topic, I will quote real life examples for each benefit.
I will also cover how asking is considered, in contrast, as an offense in reality.
2) Signs that a Team is not asking : 5 Minutes
Based on my experience as scrum master, I will share few signs in Meetings, Team members and Sprint or release which convey that team members are not asking questions.
3) 13 reasons why team members may refrain from asking : 7 Minutes
Again based on my experience, I have listed down 13 interesting reasons as to why team members may refrain from asking. I will explain each reason in brief by quoting some real life scenarios and pause at each reason for audience to think and reflect if they had been in such situation before.
4) A survey on Asking - 3 Minutes
This slide focuses on demographics of the survey which I conducted recently and I will brief on the aim for taking up the survey.
5) Team asking quotient - 5 Minutes
This slide will take the audience through the steps I have taken to calculate the "Team asking quotient" by laying the foundation on 6 important questions.
6) Value Delivery quotient : 3 Minutes
This slide will take the audience through the steps I have taken to calculate the "Value Delivery quotient" by laying the foundation on 1 important question.
7) Results from the Survey - 10 Minutes
The next two slides will focus on showcasing the results from the survey and proves my case that teams which did more asking indeed delivered value consistently.
8) Conclusion and wrap up on how to inculcate asking culture in a team: 3 Minutes
9) Questions: 5 Minutes
1) Audience will carry an acronym called REWARD for asking questions
2) The signs of teams who do not ask questions and reasons for not asking questions may help audience resonate with similar situations in future and take care of them for themselves or their teams.
3) The suggestions to nurture the culture of asking.
Agile enthusiasts, scrum masters, Managers, software developers
Prerequisites for Attendees
Minimum of 6 months experience working in a Team environment
schedule Submitted 4 months ago
People who liked this proposal, also liked:
Satya Jyoti Yellapantula - Smart way of choosing Retrospective TechniqueSatya Jyoti YellapantulaScrum MasterPegasystems
schedule 6 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.
Vamsi Krishna Kakkireni - Agile for Customer Delight – It's neither B2B nor C2C, it's H2H (Human to Human)Vamsi Krishna KakkireniScrum MasterPegasystems
schedule 5 months agoSold Out!
Surveys say that 87% of consumers would pay more to a company that provides a better overall customer experience. We can anticipate the customer needs better only by having a deeper relationship with customers. With that we can react faster to changes in the market than the market laggards.
- What is customer delight?
- Where do we stand w.r.t. customer experience?
- How to assess the maturity of our Agile processes?
- How Agile helps us in driving customer delight?
This session answers all the above questions by proposing the following:
- Assess your customer experience by calculating Customer Experience Maturity Index (CXMI)
- Assess the maturity of Agile process by calculating Agile Maturity Index (AMI)
- Hardening Index (HI) and Happiness Index (HI)
- Model drive customer delight.
This presentation will provide calculators, experiences and suggestions in achieving customer delight.