Software Development Process at UM DEI | 23rd of May 2016
•Download as PPTX, PDF•
2 likes•414 views
This document outlines a software development process using agile methodologies like Scrum and Kanban. It defines the roles of the product owner, developers, quality assurance, and delivery manager. It also describes establishing requirements and definitions of done, using continuous delivery through a pipeline, and having a team dynamic focused on agile best practices. The overall goal is to start with an idea, define its high-level scope, plan capacity, and deliver quality software incrementally using defined roles and processes.
More Related Content
What's hot
What's hot (20)
Viewers also liked
Viewers also liked (15)
Similar to Software Development Process at UM DEI | 23rd of May 2016
Similar to Software Development Process at UM DEI | 23rd of May 2016 (20)
More from Eduardo Ribeiro
More from Eduardo Ribeiro (15)
Recently uploaded
Recently uploaded (20)
Software Development Process at UM DEI | 23rd of May 2016
- 1. Software Development Process by Eduardo Ribeiro and Nuno Veloso V 1.0
- 2. Who we are?El DM Loco aka Nuno El Shadow aka Eddy
- 4. Everything starts with an idea
- 5. Release Press aka Business Case
- 6. Product also uses Kanban
- 7. High Level Scope Definition and Estimation (T-Shirt Sizing)
- 8. Capacity Planning aka Roadmap
- 9. Start and Team Speed up Product Owner Delivery Manager Developers + QA
- 10. Role Definitions and Responsibilities Product Owner Responsible for the product success. Has the vision where to take the product. Empowered: Owns the product in behalf the Stakeholders. Cares about the user needs and the business goals. Team Player: Developers + QA and Stakeholders.
- 11. Role Definitions and Responsibilities Developers
- 12. Role Definitions and Responsibilities Quality Assurance
- 13. Role Definitions and Responsibilities Delivery Manager Line Management Personal development and performance assessment. Stakeholder management Develop good, strong relations with the team’s key Stakeholders. Delivery With quality. Agile best practices Guarantee the use of agile best practices. People and culture Create a fun, safe environment worthy of the Paddy Power Betfair values. Leadership Provide guidance and steering. Component ownership Making sure that components are correctly maintained and have the adequate level of monitoring and support. Participate in product development.
- 14. Team Dynamic aka Scrum
- 15. DoR and DoD
- 16. Continuous Delivery aka our Pipeline
- 17. Questions?
- 18. Thank you!
Editor's Notes
- Commercial is strategic positioned to have all the feedback (Input) from different channels. This allow them to keep the focus on ideas generation to keep the costumers/users satisfied as well as increate the business revenue.
- If the new feature is under 55k goes directly to the Backlog. In case that is over the Product Manager needs to create a Release Press and take it to Board Evaluation. This Release Press needs to contain all the description, objectives, cost and benefits as well as KPI’s how will be validated.
- 1 Product Owner 6 Developers 1 Quality Assurance 1 Delivery Manager
- User Stories solution design Commits to what it feels it can accomplish Investigation (new solutions, new approaches, new technologies, etc.) Development (Code) Development (Automated Tests) Data Model Unit Tests Code Reviews Peer Reviews Deploys Support Demonstrations
- Commits to what it feels it can accomplish (as part of Scrum Team) Test Design Development (Automated Tests) Manual Tests Deploys Deploys Testing Support (as part of Scrum Team) Demonstrations (as part of Scrum Team)
- Delivery Teams use Scrum. Support Teams use Kanban.
- By analogy with the "Definition of Done", the team makes explicit and visible the criteria (generally based on the INVEST matrix) that a user story must meet prior to being accepted into the upcoming iteration. On a feature level, the acceptance criteria should be agreed up front BEFORE code is written. The team agrees on, and displays prominently somewhere in the team room, a list of criteria which must be met before a product increment "often a user story" is considered "done". On a feature level, the acceptance criteria should be agreed up front BEFORE the User Story is submitted to acceptance.