Your SlideShare is downloading. ×
Agile series - About Agile
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×
Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

Agile series - About Agile

498
views

Published on

This presentation is part of the series of Agile presentations shared as part of the Agile training, workshops and coaching. Focus is on providing wholesome information about using Agile beyond the …

This presentation is part of the series of Agile presentations shared as part of the Agile training, workshops and coaching. Focus is on providing wholesome information about using Agile beyond the skeleton frameworks.

Published in: Technology, Business

0 Comments
2 Likes
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total Views
498
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
24
Comments
0
Likes
2
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide

Transcript

  • 1. Copyright © Flow Cracker 2014. All other trademarks held by their respective owners.Copyright © Flow Cracker 2014. All other trademarks held by their respective owners. About Agile Speed, Scale, Skills, Simplicity http://www.flowcracker.com 1
  • 2. Copyright © Flow Cracker 2014. All other trademarks held by their respective owners. Principle Consultant – Durgaprasad B. R 2  Durgaprasad B. R  20+ Years of IT experience  B. E (E & C), Alumni of IIM,Bangalore  Certifications  PMI-PMP, PMI-ACP  SCP from Scaled Agile Academy  Durgaprasad B. R  20+ Years of IT experience  B. E (E & C), Alumni of IIM,Bangalore  Certifications  PMI-PMP, PMI-ACP  SCP from Scaled Agile Academy  Developer, Project/Program Manager, Location Delivery Head, Agile Coach  Industries: Telecom, Healthcare, Consumer Electronics, Automotive  Past few Clients: Avaya, Nortel, ALU, Microsoft, Qualcomm, Intel, Toshiba, Continental  Technologies: Web Technologies, Embedded, Legacy large systems  Developer, Project/Program Manager, Location Delivery Head, Agile Coach  Industries: Telecom, Healthcare, Consumer Electronics, Automotive  Past few Clients: Avaya, Nortel, ALU, Microsoft, Qualcomm, Intel, Toshiba, Continental  Technologies: Web Technologies, Embedded, Legacy large systems  Led large Telecom programs, IP Switches, Voice Messaging System, Contact Center, Consumer Electronics products, Automotive product development  Well versed in new age technologies as well as sun- set technologies  Trained and coached individuals and teams on Agile, Kanban, Scrum and SAFe methodologies  Regular public workshops on PMP, ACP and SAFe Certifications  Led large Telecom programs, IP Switches, Voice Messaging System, Contact Center, Consumer Electronics products, Automotive product development  Well versed in new age technologies as well as sun- set technologies  Trained and coached individuals and teams on Agile, Kanban, Scrum and SAFe methodologies  Regular public workshops on PMP, ACP and SAFe Certifications http://www.flowcracker.in/about-durgaprasad-b-r/ Contact: prasadbr@flowcracker.com. Cell: 9845558474
  • 3. Copyright © Flow Cracker 2014. All other trademarks held by their respective owners. Lean Development Toward being SAFe™ Agile Scrum Kanban XP – Extreme Programming
  • 4. Copyright © Flow Cracker 2014. All other trademarks held by their respective owners. THE OATH OF NON-ALLEGIANCE I promise not to exclude from consideration any idea based on its source, but to consider ideas across schools and heritages in order to find the ones that best suit the current situation. - DURGAPRASADhttp://oathofnonallegiance.com/
  • 5. Copyright © Flow Cracker 2014. All other trademarks held by their respective owners. Lean Development Toward being SAFe™ Agile Scrum Kanban XP – Extreme Programming `
  • 6. Copyright © Flow Cracker 2014. All other trademarks held by their respective owners. Agile Being Agile Agile MethodsAgile Manifesto & Principles
  • 7. Copyright © Flow Cracker 2014. All other trademarks held by their respective owners. Agile Timelines 1970 Waterfall by Winston Royce 1984 Borland’s software Craftsman approach 1986 Iterative development HBR paper by Takeuchi and Nonaka 1994 Dynamic Software Development Methodology (DSDM) 1995 Scrum By Ken Schwaber & Jeff Sutherland 1997 Crystal Methdologies Cockburn 1997 Rational Unified Process Grady Booch, Ivar Jacobson and James Rambaugh 1998 Feature Driven Development By Jeff De luca 1999 Extreme Programming Kent Beck 2000 Adaptive Software Development Highsmith 2001 Agile Manifesto 2003 Lean Software Development: An Agile Toolkit Mary & Tom Poppendieck 2007 Kanban System David Anderson 2012 Scaled Agile Framework Dean Leffingwell
  • 8. Copyright © Flow Cracker 2014. All other trademarks held by their respective owners. Signatories for Agile Manifesto Scrum: Mike Beedle Ken Schwaber Jeff Sutherland XP: Kent Back (TDD, Worked with Daimler Chrysler AG) Ward Cunningham Martin Fowler (Continuous Integration) Ron Jeffries DSDM (Europe) Arie Van Bennekum Crystal Clear: Alistair Cockburn Adaptive Software Development Jim Highsmith Author/Consultants: James Grenning (Planning Poker) Andrew Hunt John Korn Brian Murick Robert C Martin (Agile Alliance, Clean Code) Steve Mellor (UML, Model Driven Architecture) Dave Thomas
  • 9. Copyright © Flow Cracker 2014. All other trademarks held by their respective owners. Agile Manifesto We are uncovering better ways of developing software by doing it and helping others do it. Through this work we have come to value: Individuals and interactions over processes and tools Working software over comprehensive documentation Customer collaboration over contract negotiation Responding to change over following a plan That is, while there is value in the items on the right, we value the items on the left more.
  • 10. Copyright © Flow Cracker 2014. All other trademarks held by their respective owners. How much Agile?  Chaos Individuals and interactions Processes and Tools Working Software over Customer Collaboration Responding to Change Comprehensive Documentation Contract Negotiation Following a Plan over over over  Bureaucratic  Sweat Spot? Chaos Bureaucratic sweatspot? ?
  • 11. Copyright © Flow Cracker 2014. All other trademarks held by their respective owners. Agile Manifesto • As per COCOMO estimation model, difference between the best people making software compared to software and tools is a factor of 10:1 • Most of the activities are done by people and not tools • Motivated team outperforms unmotivated super star team • Free the team from interruptions and improve collaboration • Good work life balance. Happy teams outperform overworked team • Allow teams to generate ideas. Ideas generated by the team does not need to be sold back to the team 1. Individuals and Interactions over processes and tools
  • 12. Copyright © Flow Cracker 2014. All other trademarks held by their respective owners. Agile Manifesto • Avoid upfront detailed requirements, design, test plan, test cases when things are hazy and may change • Don’t document things till things are clear and required • Documents don’t need to be verbose. Keep it short. • Documents may be in any form : • mind map, flowchart, commented code • Avoid going wrong. Get early feedback through working prototype 2. Working software over comprehensive documentation
  • 13. Copyright © Flow Cracker 2014. All other trademarks held by their respective owners. Agile Manifesto • Need to be flexible and focus on getting things done than be punitive about things not done • Build working relationship that helps all to addresses the changing needs as the context and time changes • Don’t take rigid stand on commitments done when things were unknown 3. Customer collaboration over contract negotiation
  • 14. Copyright © Flow Cracker 2014. All other trademarks held by their respective owners. Agile Manifesto • Focus on continuous planning than a fixed plan • Responding to change includes continuous planning to accommodate change and prioritizing work items • Agile keeps cost and schedule fixed and scope flexible • Trade changes with lower priority work items in the backlog 4. Responding to change over following a plan
  • 15. Copyright © Flow Cracker 2014. All other trademarks held by their respective owners. Agile Principles 1. Our highest priority is to satisfy the customers through early and continuous delivery of valuable software 2. Welcome changing requirements, even late in development. Agile process harness change for the customers competitive advantage 3. Deliver working software frequently, from a couple of weeks to a couple of months, with a preference to 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
  • 16. Copyright © Flow Cracker 2014. All other trademarks held by their respective owners. Agile Principles 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
  • 17. Copyright © Flow Cracker 2014. All other trademarks held by their respective owners. Agile Manifesto & Quality • Agile manifesto does not mention about quality. • Implied understanding that without quality Agile will not succeed. • Excessive bugs /poor quality is a hurdle for any software methodology.
  • 18. Copyright © Flow Cracker 2014. All other trademarks held by their respective owners. Triple Constraints in Agile The Iron triangle: Assuming Quality is not negotiable in any methodology. Traditional Approach - Fixed Scope - Estimated Cost - Estimated Time Agile Approach - Estimated Scope - Fixed Cost - Fixed Time This is to certify that Mr/Mrs. Joy has run annual 10K marathon in 1 hour 6 minutes. This is to certify that Mr/Mrs. Joy has run annual 1 hour marathon covering a distance of 9.253 kilometers. Analogy: Traditional: 10 Km Marathon (variable time, fixed distance) Agile way: 1 hour Marathon (variable distance, fixed time)
  • 19. Copyright © Flow Cracker 2014. All other trademarks held by their respective owners. Agile Being Agile Agile MethodsAgile Manifesto & Principles
  • 20. Copyright © Flow Cracker 2014. All other trademarks held by their respective owners. Being Agile For sustainable success, Agile needs a combination of top leadership commitment and a culture of continuous improvement XP Scrum Kanban DFDM Lean Crystal Clear RUP User Stories, Product Backlog Pair Programming Flow, Display Boards Metaphors Coding Standards Test Automation Continuous Integration Continuous Deployment ……. Empowered Team Self Organizing Team Collaboration Transparency Servant Leadership Commitment Technical Excellence Continuous Improvement ……
  • 21. Copyright © Flow Cracker 2014. All other trademarks held by their respective owners. Being Agile The World has been trying to copy the wrong things - Mike Rother (Toyota Kata) • Methods • Tools • Best / Common Practices Agile Mindset
  • 22. Copyright © Flow Cracker 2014. All other trademarks held by their respective owners. Things to know about Agile • Agile is about culture, values than process • Agile consists of nothing more than manifesto (intent) and principles • Authors did not agree on standardizing methods. But, agreed on common manifesto and principles • Agile wisely remains silent about specifics. Thus allowing innovation and improvements • Over the years, common practices has emerged Agile treats software development as Sprint, not marathon
  • 23. Copyright © Flow Cracker 2014. All other trademarks held by their respective owners. Agile Being Agile Agile MethodsAgile Manifesto & Principles
  • 24. Copyright © Flow Cracker 2014. All other trademarks held by their respective owners. Agile Methods • Scrum, XP and Kanban are the most popular • Organizations pick and choose good practices from a buffet of practices Some Examples: XP: User stories for Requirements, estimations, release planning Scrum: Sprints, Cross functional teams DSDM/Crystal: Retrospectives Kanban: Dashboard, Flow
  • 25. Copyright © Flow Cracker 2014. All other trademarks held by their respective owners. Selective Attention test https://www.youtube.com/watch?v=vJG698U2Mvo 25 Beware of prescriptive methods. Choose your approach based on the need.
  • 26. Copyright © Flow Cracker 2014. All other trademarks held by their respective owners. About Agile Methods • Some Agile Methods (WHAT) originated even before Agile Manifesto (WHY) was written – Scrum @ Essel Corporation in 1993 • Agile manifesto and properties emerged from existing methods in 2001 – Scrum, XP, DSDM, Crystal • Some Agile methods emerged after Agile manifesto was written – Kanban, Scrumban Try to understand “WHY” before the “WHAT”
  • 27. Copyright © Flow Cracker 2014. All other trademarks held by their respective owners. Agile Methods Agile Methods enable continuous FLOW Flow, Value, Feedback, Collaboration
  • 28. Copyright © Flow Cracker 2014. All other trademarks held by their respective owners. Which Agile Method ? • Cannot compare hammer or a screw driver – If it is a nail, use hammer & – If it is a screw, use screwdriver • Scrum is the most popular. • But, there are other methods like “Kanban” which are ideal for particular type of projects, team and context • Start with some framework, and internalize it to your needs, but adhere to the Agile manifesto • Extreme Programming • Scrum • Kanban • Behavior Driven Development (BDD) • Feature Driven Development (FDD) • Crystal Clear • Dynamic Systems Development Method (DSDM) • …. Cowboy coding ? Rational Unified Process ?
  • 29. Copyright © Flow Cracker 2014. All other trademarks held by their respective owners. Why Agile? FUNDAMENTAL CHANGE or INCREASED ATTENTION TO FUNDAMENTALS ?
  • 30. Copyright © Flow Cracker 2014. All other trademarks held by their respective owners.Copyright © Flow Cracker 2014. All other trademarks held by their respective owners. Flow Cracker #7, 3rd Floor, Srishti Building, 8th Main, Basaveshwar Nagar, Bangalore - 560079 Email : prasadbr@flowcracker.com Or contactus@flowcracker.com Cell: +91 984 555 8474 Thank You 30