Our product development methodology
•Download as PPTX, PDF•
2 likes•256 views
Neil Scully, Head of Development and Service Delivery, shares the AGILE SCRUM and SPRINT process used in our product development methodology and the benefits this brings.
Recommended
Recommended
More Related Content
What's hot
What's hot (20)
Similar to Our product development methodology
Similar to Our product development methodology (20)
More from Eduserv
More from Eduserv (20)
Recently uploaded
Recently uploaded (20)
Our product development methodology
- 1. www.openathens.org Breakout Session 1 for technical roles Product Development Methodology OpenAthens Technical Q&A Neil Scully Head of Development and Service Delivery
- 2. www.openathens.org Before Scrum Requirements Analysis Design Code Test Hard to manage • Quality • Visibility • Risk • Change Contingency
- 3. SCRUM Master Development Team SCRUM Master Product Owner Product Backlog List of required developments ranked in priority order Development Team Sprint Planning Meeting Team agrees how much it can deliver in a sprint Sprint Backlog List of tasks to be developed in a sprint Daily Scrum 24 Hours 1 – 4 week sprint Sprint Review Development Team demonstrate and review completed sprint backlog items Sprint Retrospective Team reviews what went well, improvements & actions Shippable Increment Customers & Stakeholders Feature requests Fault reports Roadmap projects Development Team Product Owner Key Scrum Event Scrum Artefact Scrum Role Release SCRUM / Agile Development
- 4. www.openathens.org SCRUM benefits • Responsive to changing priorities • Better quality • More frequent releases • New features and bug fixes delivered faster • Easier to manage risks and issues
- 6. www.openathens.org DevOps • Developers, Testers and Operations working together • Using agile practices for operations • Continuous delivery • Automated testing • Automated deployment • Infrastructure as code • Virtualisation / Containerisation
- 7. www.openathens.org DevOps Benefits • Improved customer experience • Faster releases • Reduction in deployment failures and roll backs • Greater efficiency
- 8. www.openathens.org Tools Tool Issue management Jira Scrum management Jira Code review Crucible Test management TestRails Unit testing Junit Automated testing SOAPUI / Selenium Automated deployment Bamboo Code metrics Sonr Code Repository Git
Editor's Notes
- Based on Empircal theory Key principles – Transparency, Inspect, Adapt Short cycles – called sprints Each cycle delivers a product increment (complete working features that deliver the highest value to customers) Short cycles – 2 weeks - easier to manage risk and changes Adapts to shifting priorities - backlog High visibility of progress and what is being developed – review meetings, sprint board, design walk throughs Focus is on producing fully working code as early as possible Continuous improvement built in - retrospectives