Journey with XP a case study in embedded domain by Pradeep Kumar NR
Download as PPTX, PDF1 like154 views
The document discusses the journey of implementing Extreme Programming (XP) practices within Agile teams in Bangalore over two trials. The first trial faced various challenges including lack of support and leadership focus, leading to high turnover among champions. The second trial saw improvements through targeted scrum teams, resulting in self-driven teams and successful implementation of practices like Test-Driven Development and pair programming, although sustainability and customer partnership issues were noted.
Journey with XP a case study in embedded domain by Pradeep Kumar NR
- 1. 19 - 20 August 2016 Bangalore www.xpconference.in
- 2. #XPIndia2016 A journey with XP – Case study
- 3. #XPIndia2016 Lots of problems got exposed through agile practises Why we needed XP practices
- 4. #XPIndia2016 Problems All unit tests passing-All the time At the same time defects also got passed
- 5. #XPIndia2016 Problems Automate every test at the System Level Automation was a big head ache
- 6. #XPIndia2016 Problems Big sized user stories Teams situation
- 7. #XPIndia2016 Problems CI infrastructure Other problems….. Long debugging cycles Multilayered architecture Legacy Code Always spill overs
- 8. #XPIndia2016 1. Scrum teams 2. Leadership teams 3. An infra structure for CI 4. Unit tests and integration tests 5. Agile trainings What we had
- 9. #XPIndia2016 First trial of our journey Created a team of champions, from various projects Trainings on XP practices with live code Put them back to their projects
- 10. #XPIndia2016 Result after 4 sprints Leadership focused on deliveries Not Interested in Engineering practices Objectives of project change No support to champions Escalations Champions searched other jobs Don’t know how to do bla bla bla
- 11. #XPIndia2016 Second trial of our journey Identified a target project (Eligible for transformation ) Leader ship team and customer was educated 3 targeted scrum teams Sprint based goals Inspect and adapt methods
- 12. #XPIndia2016 Then came our way Not deviating much from the existing work flow, tools and technology A big heap of legacy code How to write Unit tests? Multilayered architecture- where to stop? Where to start? Different technologies in each layer No test frame works in few components Very few experts in all the areas People mind set
- 13. #XPIndia2016 What’s next? Organize teams based on features and experience Workshops Backlog with simpler user stories (Across the layers) Explore new technologies to fill up gap Brain storm on handling multi layered, multi component based architecture (Aligning tools, frame work, technologies etc )
- 14. #XPIndia2016 On the court Vertical way of tasking Deriving BDD scenarios Identify the impacted layers Deriving test pyramid Using existing tools and technologies in a different way Unit tests and its importance Integration tests Controlled coding
- 15. #XPIndia2016 After 4 sprints Less spill overs Sense of accomplishment Easy way of automating tests Easy debugging Easy integration tests No transferring defects
- 16. #XPIndia2016 Results (10 sprints) Team is self driven New champions Targeted team were 3, infected team were 6 Started TDD Pair programming New experiments One complete feature was delivered with Zero P1 defects
- 17. #XPIndia2016 What did not go well On the second engagement…. Partnering customer Partnering higher management As an opportunity to the team Sustainability We put a logical end after 6 sprints
- 18. #XPIndia2016 Where are we now One account with 9 Scrum teams is on XP (70 people ) One more account with 6 scrum teams is in the path of break through(40 people ) Third account with 7 scrum teams is not fully transformed (56 people ) 15 senior contributors infected by XP
- 21. • Questions I will try to answer from my experience