Software Development Process by Eduardo Ribeiro and Nuno Veloso V 1.0
Welcome message from author
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Transcript
Introduction to Agile
Software Development Processby Eduardo Ribeiro and Nuno VelosoV 1.0
Who we are?
El DM Loco aka NunoEl Shadow aka Eddy
Everything starts with an idea
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.4
Release Press aka Business Case
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 KPIs how will be validated.5
Product also uses Kanban
High Level Scope Definition and Estimation (T-Shirt Sizing)
Capacity Planning aka Roadmap
Start and Team Speed up
Product OwnerDelivery ManagerDevelopers + QA
1 Product Owner6 Developers1 Quality Assurance1 Delivery Manager9
Role Definitions and ResponsibilitiesProduct 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.
10
Role Definitions and ResponsibilitiesDevelopers
User Stories solution designCommits to what it feels it can accomplishInvestigation (new solutions, new approaches, new technologies, etc.)Development (Code)Development (Automated Tests)Data ModelUnit TestsCode ReviewsPeer ReviewsDeploysSupportDemonstrations11
Role Definitions and ResponsibilitiesQuality Assurance
Commits to what it feels it can accomplish (as part of Scrum Team)Test DesignDevelopment (Automated Tests)Manual TestsDeploysDeploys TestingSupport (as part of Scrum Team)Demonstrations (as part of Scrum Team)12
Role Definitions and ResponsibilitiesDelivery Manager
Line ManagementPersonal development and performance assessment.Stakeholder managementDevelop good, strong relations with the teams key Stakeholders.DeliveryWith quality.Agile best practicesGuarantee the use of agile best practices. People and cultureCreate a fun, safe environmentworthy of the Paddy Power Betfair values. LeadershipProvide guidance and steering. Component ownershipMaking sure that components are correctly maintained and have the adequate level of monitoring and support.Participate in product development.
Team Dynamic aka Scrum
Delivery Teams use Scrum.Support Teams use Kanban.14
DoR and DoD
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.15
Continuous Delivery aka our Pipeline
Questions?
17
Thank you!
Related Documents
