• Save
Agile - Natural fit for mobile application development
Upcoming SlideShare
Loading in...5
×
 

Like this? Share it with your network

Share

Agile - Natural fit for mobile application development

on

  • 1,682 views

Agile is natural fit for mobile application development, an independent consultant, Avienaash Shiralige at Endeavour's Regional Mobility Conference - India. To know about how Endeavour is different ...

Agile is natural fit for mobile application development, an independent consultant, Avienaash Shiralige at Endeavour's Regional Mobility Conference - India. To know about how Endeavour is different from other mobility companies, visit: http://www.techendeavour.com/our-value-add

Statistics

Views

Total Views
1,682
Views on SlideShare
1,682
Embed Views
0

Actions

Likes
4
Downloads
0
Comments
0

0 Embeds 0

No embeds

Accessibility

Categories

Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

Agile - Natural fit for mobile application development Presentation Transcript

  • 1. Facilitator: Avienaash ShiraligeIf youre not agile, youre not mobile Agile Buddha
  • 2. Who Am I – Avienaash Shiralige • 16+ years experience in IT Product & Service companies in various leadership roles • Agile Transformation Consultant, Workshop Facilitator, Trainer & Agile Coach • I share my opinions and experiences on my blog: http://www.agilebuddha.com • Consulting clients in Australia, Europe, US and India • Agile, Scrum, XP are my expertise areas • I conduct Agile Coaching Workshops on Scrum Basic, Advanced, Distributed Scrum, Scrum Product Owner, Agile for Management Agile Buddha
  • 3. The Right Process Produces the Right Results. Agile Buddha
  • 4. Agile - Natural Fit to Mobile Development Agile Buddha
  • 5. Agile Sprints – Support Mobile App Update Model1. Download, Install and Using the app during development sprints and post release process very similar.......2. Creates nice rhythm of sprints and releases.3. Responsive to technology changes. Agile Buddha
  • 6. Agile Increases Reliability and Leads To Continues Use of Apps 1. Mobile apps less tolerant to crashes and errors 2. Multiple cycles of testing and quality assurance helps team build-in more quality Agile Buddha
  • 7. Enables Thoughtful User Experience1. Mobile have restriction in size of the apps Sprint model helps to experiment with2. App can not take couple of minute to options and adjust the design and download features of the app in such a way that the3. Upfront restriction on application data user experience is quick, smooth and downloadable and stored locally seamless. Agile Buddha
  • 8. Mobile Apps Breathes Agile Simplicity Principle “Innovation is NOT about saying yes to everything, it’s about saying NO to all but the 20% most crucial features.” – STEVE JOBS Often 16%Sometimes You can achieve simplicity by creatively Rarely 19% filtering features, focusing only on core product features – its essence. Never 45% Agile Buddha
  • 9. Summarise….Mobile apps are different from other non-mobile applications in significant ways.1.Need to have a small footprint and download2.Update quickly and smoothly3.Seamlessly interact with back-end servers when needed4.Error free and fastThis state can only be achieved with several changes and adjustments along the way.The sprints, enhanced quality assurance, multiple test cycles, frequent customerinvolvement provide all of the necessary ingredients for mobile apps to get there. Agile Buddha
  • 10. How to Execute Large Projects Agile Way Agile Buddha
  • 11. 3 Pillars of Enterprise Agile Team Inefficient Pr e pl Team oc eo es P s Enterprise Agile Team Disorganized Disengaged Team Team Tool s
  • 12. Large Agile Team Foundation Is: Seamless and Honest Communication.
  • 13. Good Practice – 1: ONE Product Backlog Feature A Feature B Feature C Feature D Feature E Feature F Feature G Feature H Feature I Feature J €€ €€€ €€ €€€ €€ €€€ €€ €€€ €€ €€€ Team A Team B Team C Team D Team ECross functional Cross functional Cross functional Cross functional Cross functional Agile Buddha
  • 14. Good Practice – 2: Product Owner Team € Chief Product Owner € € € Product Owner Product Owner Product Owner €€ €€€ €€ €€€ €€ €€€ €€ €€€ €€ €€€ Team A Team B Team C Team D Team ECross functional Cross functional Cross functional Cross functional Cross functional Agile Buddha
  • 15. Good Practice – 3: Team StructureTraditional Silos Customer PM BA BA Analysts Designer Designers Developer Developer Developer Developer Devs Tester Tester Testers Release The Core Project Manager The Extended Team Team ideally can contain many consists of 5-9 Architect BA / Program Manager additional dedicated members Designer Tester BA members, each (7 +/- 2). playing an Developer / Core Prod. important role, but Risk SM Assessor BA Team they are typically (EXAMPLE) not dedicated to the Developer Tester Product effort. Tech Owner Security Ops Business Sponsor Agile Buddha
  • 16. Good Practice - 4: Scrum-of-Scrums PO € € Chief PO € €€ € Architect €€€ Scrum of Scrums €ATeam €B Team €C Team €D Team €E Team Agile Buddha
  • 17. Good Practice - 5: Scrum of Scrum-of-Scrums €Product Owner €€ € € Chief PO €Architect € € CXOArchitect Owner €ScrumMaster Scrum of Scrum-of-Scrums Scrum-of-Scrums Scrum-of-Scrums € € € €€ € € €€ € € € € Team C €D €E € Team A € Team B Team € Team F Team Agile Buddha
  • 18. Good Practice - 5: Distributed Daily Scrum Models UK India Isolated Scrum Teams Isolated Scrum Teams €€ €€€ €€ €€€ Independent Daily Scrums Independent Daily Scrums Daily Scrum Daily Scrum Distributed Scrum of Distributed Scrum of €€ Scrums Scrums €€ €€€ Scrum of Scrums €€€ Regular Scrum of Scrums Regular Scrum of ScrumsIntegrated Scrum Team Integrated Scrum Team €€ €€€ €€ €€€ Daily ScrumTeam members split across locations Team members split across locations Agile Buddha
  • 19. Good Practice - 6: Effectively Using Overlapping HoursLocal standup Code Commit India9:00 10:00 11:00 12:00 13:00 14:00 15:00 16:00 17:00 18:00 TIME LINE 9:00 10:00 11:00 12:00 13:00 14:00 15:00 16:00 17:00 18:00 Daily Joint Activities for Offshore and Onsite Teams UK Code Commit Agile Buddha
  • 20. Good Practice - 6: Effectively Using Overlapping Hours Agile Buddha
  • 21. Good Practice - 7: Features Teams Over Component Teams Feature Feature Feature Team A Team B Team C Story 1 Story 2 Story 3 Story 1 Story 2 Story 3 Story 1 Story 2 Story 3Presentation / User InterfaceBusiness Logic / ServicesDatabase / Integration
  • 22. Good Practice - 8: Product Owner Proxy Proxy Product Owner
  • 23. Good Practice - 9: Sprint Scheduling
  • 24. Good Practice - 10: Community of Practice
  • 25. Health Check for Agile CXO?Agile isn’t just aadevelopment issue, it applies to the entire organization. If the Agile isn’t just development issue, it applies to the entire organization. If thedevelopment team becomes Agile, but Product Management doesn’t then they will development team becomes Agile, but Product Management doesn’t then they willhinder the development team. hinder the development team. Agile Buddha
  • 26. Thank You
  • 27. Contact Me – Avienaash Shiralige• I share my opinions and experiences on my blog: http://www.agilebuddha.com• Email: avienaash@gmail.com Agile Buddha