9 Steps to Agile Adoption: a fail-safe experiment
While Agile adoption and practice is a complex model for mid/large sized Product companies to implement, we see a need for some sort of framework that can help drive it.
Why do you need to be Agile? Where do you start, when do you start, and also how do you start? These are questions that reside in most of us during early stages of adoption. Here is a 9-Step breakdown that will help companies and teams adopt multiple Agile methodologies in different situations and scenarios. Maturing it from a ‘Persona Perspective’ framework helps the ‘decision-maker’ have a case for investment, further evaluate if it works, and improve it all through!!
The discussion and idea is just my proposal that should help a team or an organization and is need not be the only way to implement Agile in an organization. Further detailing into these phases can form an overall Mindmap structure that is open to adopting from an organization and people standpoint.
Outline/structure of the Session
1. Introduction to problem statement - 5 min
2. Where do you begin at an org level and where did we fail? - 10 min
3. What was done better elsewhere and how did we learn? - 10 min
4. Step by step adoption and transition to Agile from any other mehodology you may have. - 10 min
5. Q & A
Fail safe method of Agile adoption at an organization, presented in about 35 mins. These include experiments and learnings collected across various teams and companies that lead to organized method of adoption. it is definitely worth spending 45 mins of your time to take away 2 years of learning.
Anyone adoptiing Agile at organization level and want to take advantage of fail-safe learnings
schedule Submitted 3 years ago
People who liked this proposal, also liked:
Sachin Natu / Naresh Jain - Inverting Test Pyramid - A First Hand Experience ReportSachin NatuSr. Manager QAIDeaS a SAS CompanyNaresh JainFounderConfEngine.com
schedule 4 years agoSold Out!
Test automation is extremely crucial in adoption of an agile delivery. However, it can take one for a ride, if the approach is not correct. In this sensational, heart throbbing, experience report, we'll share our story of how we turned around an inefficient, expensive automation style to lean, efficient style. In addition to sharing a real-world example, we'll also share some of the key challenges we faced and how we solved them. If you are convinced about the Testing Pyramid, but are struggling to invert it, then this session is for you.
Earlier Defect Detection - Higher test coverage at Unit/Intermediate layers lead to earlier defect detection. Reduced number of issues found on higher test environments/Production. Reduced cost of defect fixing.
Reduced maintenance cost - UI tests are fragile and costlier to maintain Vs backend tests. No of changes in services layer are comparatively less.
Reduced test execution time - Backend tests are much faster. Almost 7-10 times faster than UI Tests - improved build certification time.
Test feedbacks are naturally distributed across layers of application. Test feedbacks are more pin pointed/ granular.
Naveen Indusekhar - Research paper on 'What happens to Engineering Manager in Agile world'Naveen IndusekharNaveen (Sr. Program Manager) and JP (Sr. Engineering Manager)McAfee, an Intel Company
schedule 3 years agoSold Out!
This is an extremly simple topic with a very complex answer. I have spent last 3 years experimenting and working with lot of people to understand what happens to the so called Manager role in Agile world. With a self organizing, empowered team, does Manager still have a role? Do you shelve these senior people who drove all your deliverables in the past for your company? Do you just let go the technical expertize these people bring along?
The research information around the experiment and results will be shared and am very positive that this will help lot of organizations move forward with great benefits. We will see how certain gaps that are created with introduction of Agile can be solved through these senior professionals. At the same time teams don't need to compromize or business doesn't need to compromize on new found agility by adopting any of the Agile practices.
The very next discussion that I will touch base as part of this presentation is the role of Project Leads. Many Leads resist movement to Agile because they feel their growth will now be stagnated. Is this true? It is again an interesting data set captured by talking to Leads in waterfall world and understanding what they really aspire for.
Looking forward to sharing my insights with real implementation and resulting data that I'm sure each of you will benefit from.
Pooja Wandile - Scaling Scrum To Large Distributed Teams and its ChallengesPooja WandileAssociate Director-ProjectsCognizant Technology Solutions
schedule 3 years agoSold Out!
As designed for use, Scrum works well for small co-located teams, cross functional teams. As the popularity of Scrum starting growing, more and more companies started adopting Scrum with mixed results. But overall, the trend has been increasing. Off late, big enterprises have also started adopting agile for their business needs and building complex products. In a recent study, the number of enterprise customers adopting scrum has doubled in last 2 years and they have used distributed scrum on large programs. So, the question is, can agile scale beyond small and co-located teams and what challenges could be there?
This presentation talks about our experience of implementing scrum on a large program, the challenges of scaling scrum and how to overcome these challenges.