Agile project discovery
- 2. Agenda 1. Introductions 2. Introduction to SDLC 3. Why Agile SDLC 4. Scrum 5. Project Discovery 2
- 3. Introduction
- 4. Introduction SDLC Software Development Life Cycle -Continuous process - Different SDLC - All methodologies follow the below basic stages 4 31 2 54
- 5. SDLC Models - Waterfall Model - Iterative Model - Spiral Model - V-Shaped Model - Agile Model 5
- 7. “ You’ve got to start with customer experience and work back towards the technology - not the other way around 7 Steve Jobs
- 8. AGILE SDLC - Ag.ile - move quickly and easily, well coordinated and adaptable. - Considered Lightweight - People-based rather than plan-based - Feedback-driven development in short iterations - Project divided by short and transparent iterations - Risks are minimized thanks to flexible change process - Fast release of first version - Agile Manifesto - defines with set of principles
- 9. Agile Manifesto - A Statement of Values - While we value in the items on the right , we value the items over the left more Responding to Changes 04 Over following a Plan Customer Collaboration 03 Over Contract Negotiation Working Software02 Over comprehensive Documentation Individuals and interactions over 01 Over Processes and Tools
- 10. Agile in Practice - Focus on Business Value - Work together closely as one team - Work in Short iterations - Inspect and Adapt - Remove waste effectively ( wasted efforts, wasted time) - Delivery Working Software early and often Agile Development Value Proposition Visibility Risk Traditional SDLC Agile SDLC Adaptability Business Value
- 11. Scrum - Scrum is a agile process that allows us to focus on delivering highest business values in the shortest time. - It allows us to rapidly and repeatedly inspect actual working software/ product ( Inspect and Adapt). - Business sets the priorities. Teams self-manage to determine the best way to deliver the highest priority features. - Iterations ( sprints are Time bound). - At every ( pre-decided) frequency any one can see real working software/product and ( decide for product release or) continue to enhance for another iteration
- 12. Scrum Framework Roles: - Product Owner - Scrum Master, Project Manager - Team ( Developer, Tester, QA) Ceremonies: - Sprint Planning, Sprint Review, Sprint Retrospective, Daily Scrum Meeting /Stand-up Meeting. Artifacts: - User Stories, Epics,Product Backlog, Sprint Backlog, Burndown Chart, Velocity, Control Charts.
- 13. Implementation Cycle Scrum in a Page Analysis Product Backlog Sprint Execution 1 to 2 Week Sprint Daily Standup Meeting TEST Input from end users, customers , teams and stakeholders Product Owner Features Sprint Planning Team selects how much to commit to by Sprints End Team Potentially Shippable Product Product Backlog refinement
- 14. Project Discovery Successful Problem Solving requires finding the right solution to the right problem. We fail more often because we solve the wrong problem than because we get wrong solution to the right problem Russell L Ackoff. 14
- 15. 15 How the Discovery Process Works Objective What we need to Know Hypothesis What we already Know Methods Filling in the gaps. Conclusion What we have learned, to prepare a MVP. Conduct Gather Data and Information
- 16. 16 Objective : What we need to know - Understand from customer’s perspective - Vision of the Solution that we are trying to solve - Sketch what is desired from the initiative
- 17. 17 Hypothesis : What we already know - Existing Business process and policies - Infrastructure and Technology - Organizational Culture - Stakeholders Thresholds to Change - Organizational Priorities and needs
- 18. 18Method : Filling in the gaps - Requirements Gathering - Customer interviews - Customer questionnaires - Stakeholder interviews. - MoSCoW Prioritization and Analysis Method. - Current Workflow and touch points - Desired Workflow (mapping).
- 19. 19 - User stories - Features : MoSCoW - Sketch the suggested user flow - User journey - Visual Direction ( Wireframe) Conduct : Gather Data and Information.
- 20. 20 - Design Direction - Architecture and Security - Minimum Viable Product - User story delivery and budget ( time and cost). Conclusion
- 21. Thanks! Any questions? You can find me at asrrhmn@outlook.com 21