The document discusses the concept of distributed agile development, highlighting its necessity, challenges, and solutions. It emphasizes the Agile Manifesto principles, such as prioritizing customer satisfaction and continuous delivery of valuable software, while also addressing the complications arising from distributed teams like time zone differences and reduced team expression. Lastly, it offers guidelines for effective agile ceremonies and tools to enhance collaboration in distributed agile environments.

1. Distributed Agile -
Next Gen Agile?
1

2. Manu Chopra
Based in Gurgaon, IN
• 16+ year’s of diverse experience working on Oracle
Products – Oracle EBS V11 and V12, Infrastructure, Oracle
Cloud
• Oracle Architect - Background in Technical consulting, Large
scale Portfolio/Delivery management
• Agile/DevOps Practitioner, Certified SAFe Program
Consultant (SPC4.0), Certified Scrum Professional (CSP)
• Experience in project and program management with
significant business transformation component
• Interest in exploring new things. Traveller by hobby, Love to
do Road trips on my Bike/Car. Passionate about Cricket and
Hockey. Appreciate healthy debates
Introduction

3. Agenda
• Distributed Development,
• Why?
• Problems.
• can lead to…..
• Side Effects?
• Solution?
• Agile/Distributed Agile
• Scrum
• Kanban
• Safe
• Challenges of Distributed Agile
• Must do in Distributed Agile
• Agile Ceremonies – Daily Stand up
• Tools

4. Distributed Development– ?
Distributed Development, Why?

5. Distributed Development– Need

6. Distributed Development– Need

7. Distributed Development– Need

8. Distributed Development– Problems
•
Distributed Development, Problems?

9. Distributed Development– Problems
•

10. Distributed Development– Problems
•

11. Distributed Development– Problems
•

12. Distributed Development– Problems
•

13. Distributed Development– Problems
•

14. Distributed Development– Problems
•

15. Distributed Development– Problems
•

16. Distributed Development– Problems
•

17. Distributed Development– Control Mechanism
•
Distributed Development, Can lead
to……….

18. Distributed Development– Control Mechanism
•

19. Distributed Development– Control Mechanism
•

20. Distributed Development– Control Mechanism
•

21. Distributed Development– Control Mechanism
•

22. Distributed Development– Effects
•
Distributed Development, Side Effects?

23. Distributed Development– Side Effects
•

24. Distributed Development– Side Effects
•

25. Distributed Development– Side Effects
•

26. Distributed Development– Side Effects
•

27. Distributed Development– Solution
•
Distributed Development – Solution
for Problems?

28. Distributed Development– Solution
•
Distributed Agile ?

29. Distributed Development– Solution
The Agile Manifesto
Individuals and interactions over processes and tools
Working software over comprehensive documentation
Customer collaboration over contract negotiation
Responding to change over following a plan
We are uncovering better ways of developing software by doing it and helping others do it.
Through this work we have come to value:
That is, while there is value in the items on the right, we value the items on the left more.

30. Distributed Development– Solution
The Agile Manifesto
1. Our highest priority is to satisfy the customer through early and continuous delivery of valuable
software.
2. Welcome changing requirements, even late in development. Agile processes harness change for the
customer's competitive advantage.
3. Deliver working software frequently, from a couple of weeks to a couple of months, with a preference
for the shorter timescale.
4. Business people and developers must work together daily throughout the project.
5. Build projects around motivated individuals. Give them the environment and support they need, and
trust them to get the job done.
6. The most efficient and effective method of conveying information to and within a development team
is face-to-face conversation.

31. Distributed Development– Solution
The Agile Manifesto
7. Working software is the primary measure of progress.
8. Agile processes promote sustainable development. The sponsors, developers, and users should be
able to maintain a constant pace indefinitely.
9. Continuous attention to technical excellence and good design enhances agility.
10. Simplicity—the art of maximizing the amount of work not done—is essential.
11. The best architectures, requirements, and designs emerge from self-organizing teams.
12. At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its
behavior accordingly.

32. Distributed Development– Scrum

33. Distributed Development– Kanban

34. Distributed Development– Safe

35. Distributed Agile– Challenges
Time Zone Differences
Commonality of Purpose may get defeated
Self Organization behavior is compromised
Lack of Team Expression and participation

36. Distributed Agile– Challenges

37. Distributed Agile– Ceremonies
•
Distributed Agile– How to Have Team
Standups/Daily Scrums?

38. Distributed Agile– Ceremonies - Standups
•
Timings – Should Suit Everyone
Do not Skip Your Standups
Do it Standing

39. Distributed Agile– Ceremonies - Standup
•

40. Distributed Agile– Ceremonies - Standup
•

41. Distributed Agile– Ceremonies - Standup
•

42. Distributed Agile– Lets Play
• Download Kahoot App
• Create your profile – if needed
• Enter the Game Pin “0359851” to play
https://kahoot.it/challenge/0359851

43. 43