Download to read offline
Uploaded byEduserv
Our product development methodology
The document discusses a breakout session on product development methodologies focusing on Scrum and DevOps. It outlines Scrum's key roles, events, and artifacts, highlighting its benefits such as improved responsiveness and quality. Additionally, it details DevOps practices and benefits, emphasizing collaboration and efficiency in software delivery.
More Related Content
Similar to Our product development methodology
Our product development methodology
- 1. www.openathens.org Breakout Session 1for technical roles Product Development Methodology OpenAthens Technical Q&A Neil Scully Head of Development and Service Delivery
- 2. www.openathens.org Before Scrum Requirements AnalysisDesign Code Test Hard to manage • Quality • Visibility • Risk • Change Contingency
- 3. SCRUM Master Development Team SCRUMMaster 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 • Responsiveto changing priorities • Better quality • More frequent releases • New features and bug fixes delivered faster • Easier to manage risks and issues
- 5.
- 6. www.openathens.org DevOps • Developers, Testersand 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 • Improvedcustomer experience • Faster releases • Reduction in deployment failures and roll backs • Greater efficiency
- 8. www.openathens.org Tools Tool Issue management Jira Scrummanagement Jira Code review Crucible Test management TestRails Unit testing Junit Automated testing SOAPUI / Selenium Automated deployment Bamboo Code metrics Sonr Code Repository Git
- 9.
Editor's Notes
- #4 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