Don't drive your Race car on a dirt track!! - Athresh Krishnappa, Scrum Bangalore 22nd Meetup22nd
•
0 j'aime•63 vues
The document discusses applying agile and DevOps methods to solve challenges in developing a new product portal for an e-commerce company. A self-organized agile team was formed consisting of developers, QA analysts, UX designers, a product owner, and scrum master. The team analyzed the current development process, identified waste, and aspired to improve customer experience, quality, and on-time delivery. The team exhibited insights from metrics on code quality and velocity to guide their solution of implementing continuous integration/delivery and an engineering insights platform. Reflections found improved practices, tools adoption, and lessons around communication and infrastructure needs. Challenges around technology changes and performance expectations were overcome.
![Table Of Content
1. Challenge/Opportunity identified to resolve
2. Form Self-Organized Team
3. Assess Current Value Stream
4. Define Aspired Goal [Tangible/Intangible]
5. Analysis & Inference
6. Apply Solution [Lean-Agile methods chosen to solve]
7. Exhibit working Solution
1. Show Benefits [Tangible/Intangible]
8. Share Reflection Outcome
1. Lessons Learnt/Smart Tips
2. Your inference on Industry Practices
9. Controls for Consistency
10.State Challenges faced while applying solution
11.Message to the World!
1. Challenge/Opportunity
2. Self-Organized Team
3. Current Value Stream
4. Aspired Goals
5. Analysis & Inference
6. Apply Solution
7. Exhibit Solution
8. Reflection Outcome
9. Controls for Consistency
10. Challenges faced
11. Message to the World](data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7)
Recommandé
Contenu connexe
Tendances
Tendances (20)
Similaire à Don't drive your Race car on a dirt track!! - Athresh Krishnappa, Scrum Bangalore 22nd Meetup22nd
Similaire à Don't drive your Race car on a dirt track!! - Athresh Krishnappa, Scrum Bangalore 22nd Meetup22nd (20)
Plus de Scrum Bangalore
Plus de Scrum Bangalore (20)
Dernier
Dernier (20)
Don't drive your Race car on a dirt track!! - Athresh Krishnappa, Scrum Bangalore 22nd Meetup22nd
- 1. Do not drive a Race car on a Dirt Track! Athresh Krishnappa Brillio Technologies Scrum Bangalore Meetup- 30th June 2018
- 2. Table Of Content 1. Challenge/Opportunity identified to resolve 2. Form Self-Organized Team 3. Assess Current Value Stream 4. Define Aspired Goal [Tangible/Intangible] 5. Analysis & Inference 6. Apply Solution [Lean-Agile methods chosen to solve] 7. Exhibit working Solution 1. Show Benefits [Tangible/Intangible] 8. Share Reflection Outcome 1. Lessons Learnt/Smart Tips 2. Your inference on Industry Practices 9. Controls for Consistency 10.State Challenges faced while applying solution 11.Message to the World! 1. Challenge/Opportunity 2. Self-Organized Team 3. Current Value Stream 4. Aspired Goals 5. Analysis & Inference 6. Apply Solution 7. Exhibit Solution 8. Reflection Outcome 9. Controls for Consistency 10. Challenges faced 11. Message to the World
- 3. 1. SPORTS CAR –DIRT TRACK SYNDROME TOC Indicator: 1. Interesting Title 2. Challenge/Opportunity 3. Self-Organized Team 4. Current Value Stream 5. Aspired Goals 6. Analysis & Inference 7. Apply Solution 8. Exhibit Solution 9. Reflection Outcome 10. Controls for Consistency 11. Challenges faced 12. Message to the World Agile + DevOps: Drives focus on Speed Reality: is a lot like driving a sports car on a dirt track Need: Create a Smooth track How do we Do it?
- 4. Drive Fast and Drive in the right direction… 20Kms Destination CAUTION: Curve Ahead
- 5. 2. Challenge or opportunity “No Time for rework Had to get things right, the first time” TOC Indicator: 1. Interesting Title 2. Challenge/Opportunity 3. Self-Organized Team 4. Current Value Stream 5. Aspired Goals 6. Analysis & Inference 7. Apply Solution 8. Exhibit Solution 9. Reflection Outcome 10. Controls for Consistency 11. Challenges faced 12. Message to the World Time to Market Requirements Volatility Everything New!! Aggressive schedules New Logo | New Team | New Technology Evolving Requirements Around 3000 orders placed each week through the portal Page should load in less than 3 seconds with accurate data Complex calculation algorithm that accounts for around 40 scenarios for 3000 order groups Data on the portal should be updated near-real-time at least every 15 minutes
- 6. Hi! I am James, Product Owner I prioritize the product backlog. Ensured each iteration got adequate attention at requirements Hey! I am Priya, Proxy Product Owner I help PO in prioritization and writing user stories Together we form self organized & on shore - off shore team !!! Hi! I am Sid, Agile Coach I constantly guide the team in a subtle, self correcting manner Hello! I am Gowri Shankar, Scrum Master – Servant Leader • I make sure my team lives by the value and practices of Scrum • I also be thought of as a process owner for the team, creating a balance with the project's key stakeholder, who is referred to as the product owner We Folks! are Cross functional - Development Team • We have Developers, QA analysts & UI/UX who constantly question PO & PPO on requirements • We challenge each other on implementation to find the right solution • Every team member is aware of ALL requirements: doubling up for one another was easy • QA constantly measuring the product against the SLAs and highlighting issues to all stakeholders • Every artifact that goes to production is aggressively inspected by us before release • Each release had an identified champion “Brillian of the Sprint”: - hierarchy agnostic decision Let’s meet the team!!! TRANSPARENCY TOC Indicator: 1. Interesting Title 2. Challenge/Opportunity 3. Self-Organized Team 4. Current Value Stream 5. Aspired Goals 6. Analysis & Inference 7. Apply Solution 8. Exhibit Solution 9. Reflection Outcome 10. Controls for Consistency Hi! I am Luther, Technical Architect • I am responsible for defining the overall structure of a program or system • Ensuring all parts of the project run smoothly Finally!! WE DO CELEBRATE SPRINT SUCCESS ☺ I am Suman, Delivery Manager, I bridge the gap between customer and team to ensure a great Customer Experience
- 7. 4. Our Value Stream TOC Indicator: 1. Interesting Title 2. Challenge/Opportunity 3. Self-Organized Team 4. Current Value Stream 5. Aspired Goals 6. Analysis & Inference 7. Apply Solution 8. Exhibit Solution 9. Reflection Outcome 10. Controls for Consistency 11. Challenges faced 12. Message to the World CONTINUOUS DELIVERY SOURCE CODE REPOSITRY COMMIT NOTIFY TARGET ENVIRONME NT END THE PROCESS END THE PROCESS END THE PROCESS CONTINUOUS INTEGRATION ( C I ) CONTINUOUS DEPLOYMENT BUILD TEST QUALITY CHECK TARGET ENVIRONMENT REQUIREMENTS JENKINS ANISBLE GITHUB CONTINUOUS Monitor( C M ) Data Ingest Analyze Visualize Process flow of the system automated from manual Step#1: Requirement Elicitation + Code Step#2: Build Step#3: Code Review Step#4: Deploy Step#5: UAT / SIT Step#6: Monitor + Support PO + TEAM Waiting Time: 12Hrs Requirement Gap: 10Hrs Manual Traceability: 08Hrs ------------------------------------ Waste Reduction: 20Hrs PPO + TEAM Manual Build: 10Hrs --------------------------------- Waste Reduction: 10Hrs Manual Review: 15Hrs --------------------------------- Waste Reduction: 15Hrs Manual Deploy: 16Hrs --------------------------------- Waste Reduction: 16Hrs Manual Monitor: 16Hrs --------------------------------- Waste Reduction: 16Hrs
- 8. 5. Aspired Goals TOC Indicator: 1. Interesting Title 2. Challenge/Opportunity 3. Self-Organized Team 4. Current Value Stream 5. Aspired Goals 6. Analysis & Inference 7. Apply Solution 8. Exhibit Solution 9. Reflection Outcome 10. Controls for Consistency 11. Challenges faced 12. Message to the World CUSTOMER EXPERIENCE Score Minimum 8 out of 10 Deliver a HIGH QUALITY PRODUCT Deliver ON TIME There is always a better way– find it fast !!!
- 9. 6. Analysis & Inference Static Code Analysis Inference: • Co-relation between technical debt and duplicated blocks • Technical debt increases when duplicated blocks increases TOC Indicator: 1. Interesting Title 2. Challenge/Opportunity 3. Self-Organized Team 4. Current Value Stream 5. Aspired Goals 6. Analysis & Inference 7. Apply Solution 8. Exhibit Solution 9. Reflection Outcome 10. Controls for Consistency 11. Challenges faced 12. Message to the World
- 10. 6. Analysis & Inference – Cont.., Velocity Predictive Analysis Inference: • Predicting teams velocity based on the actual velocity captured from previous sprints TOC Indicator: 1. Interesting Title 2. Challenge/Opportunity 3. Self-Organized Team 4. Current Value Stream 5. Aspired Goals 6. Analysis & Inference 7. Apply Solution 8. Exhibit Solution 9. Reflection Outcome 10. Controls for Consistency 11. Challenges faced 12. Message to the World
- 11. 6. Analysis & Inference – Cont.., Defect Pareto Analysis Inference: • % of defects captured in every module • We can focus on improving the code quality and reducing the defect count in couple of modules to reduce the overall defect count TOC Indicator: 1. Interesting Title 2. Challenge/Opportunity 3. Self-Organized Team 4. Current Value Stream 5. Aspired Goals 6. Analysis & Inference 7. Apply Solution 8. Exhibit Solution 9. Reflection Outcome 10. Controls for Consistency 11. Challenges faced 12. Message to the World
- 12. 7. Apply Solution: Our Engineering Insights Platform PROJECT HEALTH RELEASE PREDICTIBILITY ACTIONABLE INSIGHTS TEAM PERFORMANCE Our Engineering and Process Insights Platform TOC Indicator: 1. Interesting Title 2. Challenge/Opportunity 3. Self-Organized Team 4. Current Value Stream 5. Aspired Goals 6. Analysis & Inference 7. Apply Solution 8. Exhibit Solution 9. Reflection Outcome 10. Controls for Consistency 11. Challenges faced 12. Message to the World
- 13. 8. Exhibit Solution TOC Indicator: 1. Interesting Title 2. Challenge/Opportunity 3. Self-Organized Team 4. Current Value Stream 5. Aspired Goals 6. Analysis & Inference 7. Apply Solution 8. Exhibit Solution 9. Reflection Outcome 10. Controls for Consistency 11. Challenges faced 12. Message to the World
- 14. 9. Reflection Outcome TOC Indicator: 1. Interesting Title 2. Challenge/Opportunity 3. Self-Organized Team 4. Current Value Stream 5. Aspired Goals 6. Analysis & Inference 7. Apply Solution 8. Exhibit Solution 9. Reflection Outcome 10. Controls for Consistency 11. Challenges faced 12. Message to the World
- 15. 9. Reflection Outcome TOC Indicator: 1. Interesting Title 2. Challenge/Opportunity 3. Self-Organized Team 4. Current Value Stream 5. Aspired Goals 6. Analysis & Inference 7. Apply Solution 8. Exhibit Solution 9. Reflection Outcome 10. Controls for Consistency 11. Challenges faced 12. Message to the World Customer CIO to Brillio CEO: “you guys killed the buyer portal project (our way of saying you did a terrific job !!) , we went live and our president was very impressed. “ Head of Merchandising Quoted... “…Merchandising Portal. It looks great, it’s easy to use and is now fully operational .. will be a huge benefit to the Buyers, helping them to be more efficient, minimize waste, improve fill rates and improve quality management. It ultimately will benefit our customers by having the best quality products on our shelves”
- 16. 9. Reflection Outcome - Continuation TOC Indicator: 1. Interesting Title 2. Challenge/Opportunity 3. Self-Organized Team 4. Current Value Stream 5. Aspired Goals 6. Analysis & Inference 7. Apply Solution 8. Exhibit Solution 9. Reflection Outcome 10. Controls for Consistency 11. Challenges faced 12. Message to the World Practices • End to End Scrum practices implementation • Clear cut roles identification • More involved team members – estimation, sprint planning, back log refinement - all done by team • Complete visibility of progress on tool – JIRA, BOLT Tools Adoption • JIRA – For Engineering Implementation tracking • SonarQube – For Static Code Analysis • Jenkins – Orchestration Platform for Continuous Integration • BOLT – for real-time visualization of project indicators Lessons Learnt: • Communication gap between on-shore and off-shore team to be avoided by better collaboration or team collocation • DoR & DoD to be finalized by PO and Team to avoid requirement conflicts • Infrastructure setup & dependencies must be ready and validated before sprint starts
- 17. 10. Controls for consistency TOC Indicator: 1. Interesting Title 2. Challenge/Opportunity 3. Self-Organized Team 4. Current Value Stream 5. Aspired Goals 6. Analysis & Inference 7. Apply Solution 8. Exhibit Solution 9. Reflection Outcome 10. Controls for Consistency 11. Challenges faced 12. Message to the World Customer Involvement Engineering and Process Insights Introduced Brillian of the Sprint Team EmpowermentTransparency
- 18. 11. Challenges Faced TOC Indicator: 1. Interesting Title 2. Challenge/Opportunity 3. Self-Organized Team 4. Current Value Stream 5. Aspired Goals 6. Analysis & Inference 7. Apply Solution 8. Exhibit Solution 9. Reflection Outcome 10. Controls for Consistency 11. Challenges faced 12. Message to the World - Resolution Challenges • Technology Changes midway • Performance expectations • Proof of concept validation • Implemented In-Process performance testing
- 19. 12. Your Message to the world TOC Indicator: 1. Interesting Title 2. Challenge/Opportunity 3. Self-Organized Team 4. Current Value Stream 5. Aspired Goals 6. Analysis & Inference 7. Apply Solution 8. Exhibit Solution 9. Reflection Outcome 10. Controls for Consistency 11. Challenges faced 12. Message to the World Agile and DevOps fuels the team for SPEED. However its important to speed in the right direction. Actionable insights from data often lost in tools silos, can be leveraged to push agility, speed and culture to greater heights
- 20. THANK YOU!