Why Agile

1,284 views

Published on

Published in: Technology, Business
0 Comments
1 Like
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
1,284
On SlideShare
0
From Embeds
0
Number of Embeds
78
Actions
Shares
0
Downloads
0
Comments
0
Likes
1
Embeds 0
No embeds

No notes for slide

Why Agile

  1. 1. Why Agile? Srijan Technologies Pvt. Ltd.
  2. 2. Why projects fail in a traditional delivery model Srijan Technologies Pvt. Ltd.
  3. 3. Why projects fail in a traditional delivery model Gaps between what customer expects and what was delivered Srijan Technologies Pvt. Ltd.
  4. 4. Why projects fail in a traditional delivery model Risk of miscommunication between Client Business Analyst Project Lead Developers, is high Srijan Technologies Pvt. Ltd.
  5. 5. Other problems with such a delivery model It is nearly impossible to capture and document ALL features at the concept stage of a project [it also not an advisable project/product development strategy] Lack of clarity in feature specification leads to poor estimates – either they are over-estimated or under-estimated --> and both these situations are bad for the project Project failure rate in terms of delivery-on-time is high Cost over-runs Vendors cut-corners (when they are cornered!) During development, business/client teams request changes in features with evolving project/business goals; adapting these is really difficult Srijan Technologies Pvt. Ltd.
  6. 6. Enter Agile  Agile, by definition means, a software development method where requirements and solutions evolve through collaboration between self- organizing, cross-functional teams  It promotes adaptive planning, evolutionary development and delivery, a time- boxed iterative approach, and encourages rapid and flexible response to change How Agile worksSprint 1 Sprint 2 Sprint X Srijan Technologies Pvt. Ltd.
  7. 7. Enter Agile : what this means Breaks down the project into an induction, development and transition phase Contracts can be defined for such stages of project evolution/development Incorporating “new ideas” or “yet better options” into project development lifecycle is manageable Srijan Technologies Pvt. Ltd.
  8. 8. Srijans adaptation of Agile : Induction phase A typical Scrum team structure for the induction phase constitutes: – Technical Architect Scrum Master, Developer(s) – from Srijan – Product Owner – from the client side Requirements gathering is done with active involvement of the entire Scrum Team, and additional stakeholders from the client side, as needed A product backlog alongwith other supporting documentation such as wireframes, or even prototypes are prepared during this phase The development phase scope, time and contract is defined based on the estimates for features identified during the induction period Estimates for transition phase can be agreed upon. Srijan Technologies Pvt. Ltd.
  9. 9. Srijans adaptation of Agile : Induction phaseHow does this help: Since a whole project team is collaborating, risk ofmiscommunication is greatly reduced Is reduced to Srijan Technologies Pvt. Ltd.
  10. 10. Srijans adaptation of Agile : Development phase Development of the product is done in several Sprints. Each Sprint spans upto 2 weeks Daily Stand-ups – ideally, a Product Owner is an part such daily meetings with the rest of the Scrum Team. Agenda: – What was done yesterday – What will be done today – What are the hurdles faced A demo is given to Product Owner at each sprint-end. This enables early feedback, course correction (changes, misunderstandings in scope), measure speed of development (velocity) The Scrum Team is enhanced by adding more developers, front-end engineers and QA engineers, as estimated in induction phase Srijan Technologies Pvt. Ltd.
  11. 11. Srijans adaptation of Agile : Development phase How does this help: Continuous client feedback and course correction allows for induction of change requests and feature additions within sprints Gap between customer expectation and final product is reduced. Srijan Technologies Pvt. Ltd.
  12. 12. Srijans adaptation of Agile : Transition phase Transition period usually involves – installation of the product to the live site for beta release – User Acceptance Testing [UAT] – Bug Fixing / Change Requests – Training – Final Sign-off Intense client [Product Owner] engagement through UAT, QA and training. During the transition phase we keep only one developer full-time to fix bugs and carry out operations. The SCRUM Master and QA Engineer coordinate with the Server administration team are used part-time to help in testing and training. Stake Holders [may] test the site as part of beta release Srijan Technologies Pvt. Ltd.
  13. 13. Srijans adaptation of Agile : Transition phaseHow does this help : UAT helps make the product more stable and beta productcan even be tested internally before being rolled out to public. Testing Internal and beta UAT testing Srijan Technologies Pvt. Ltd.
  14. 14. How is Srijans model different from others Agile by the book asks for the team to be staffed for the whole duration of the project starting from induction However, at Srijan, we understand that not all clients like this idea of staffing a fat team during induction itself , where only a couple of roles may suffice Similarly, a Technical Architect is not required in most cases during the transition phase! Contracts for induction, development and transition phases are separated The client gets what they pay for!! Srijan Technologies Pvt. Ltd.
  15. 15. How does all this help the client? Greater project control Regular done-done deliverables; small wins, continuously You-get-what-you-pay-for Staffing team optimally for each phase Better tested and quality product Training and management/stakeholder acceptance happens continually Remote Management Greater client satisfaction as the product meets desired goals/objectives Srijan Technologies Pvt. Ltd.
  16. 16. Why Agile?Thank you!Get in touchInterested in setting up an Agile Team withSrijan? Write to us: business@srijan.in Srijan Technologies Pvt. Ltd.

×