Scrum Methodology

  User Story Detailed, valuable chunk of work a team can quickly deliver. I ndependent N egotiable V aluable E stimable S mall T estable Format for user story As a <user role>, I want <user requirement> so that <desired benefit> Functional User Story As a   mobile customer,  I want to create a profile  so that future orders are faster to place Nonfunctional Story Work that supports users without directly benefiting them Example: As a developer , I want to upgrade the database software to the latest version so that we have a supported product. Acceptance Criteria (AC) AC must be as explicit as possible. Example Customer name is captured and saved Customer email address is captured and saved. Customer phone number is captured and saved. Customer password is captured and saved.

  Product Vision Serves as a guide for your team. Established by the product owner. Minimum Viable Product When a product has been developed just enough to get user feedback: Allows for a fast feedback loop. Reduces scope creep or gold plating where unnecessary things are added along the way Product Vision example Help busy professional have more time and feel healthier by providing a mobile app where they can quickly order an affordable, tasty, healthy lunch and have it delivered or pick it up themselves. Decomposing a Vision   Identify themes Example Themes Profile Order Payment Delivery Themes trigger development ideas Themes group work for efficiency and security Break themes into features Features: Login Save Password Recent Orders Favorites Recent Locations Product Owner may say that they need less features or others

  Product Owner (PO) Responsibilities Acts as the full-time business representative. Review the team's work. Ensures highest value is delivered. PO is always ordering the work and ensuring the team members clearly understand the details of the requests. Interacts with skateholders, its not enough to interact with the team members, they must also be in tune with all the changes that are ocurring in the business context. Maintains the product vision, manages the backlog of work to be done and prioritization of the work items. Since time and costs are locked, the PO is painfully aware that the work must be continuously sorted to highest value first. They'll also be pushing the team to complete as much work as possible in each short delivery period. PO focuses on what needs to be done. REMEMBER The Scrum approach allows the scope to be flexible. Scum Master Responsibilities Protects the team and its processes. Keeps the team within the guardrails of scrum. They balance the demands ...

 Traditionally, waterfall project teams face three constraints: Time Cost Scope They are unable to change any of these things once the projects starts. The problem is that the bussiness environment changes around us. This means that by the time we're done. What we build is no longer valuable. This isn't anyone's fault. Business needs are changing more rapidly than ever. Projects requirements are shifting just as quickly to keep up. So teams were doomed to failure on every project until the agile manifesto came along. Then we shift our focus away from constraining all three project elements and decided to make one of them flexible scope and fixed cost. All agile methodologies follow that first key paradigm shift. Lock everything but scope and you've got yourself a framework that will deliver exactly what's needed as  quickly as possible. Agile is a broad umbrella of many methodologies that follow the same principles. Scrum is one of them. Scrum took it a step further...

 Work with business partners throughout a project. Measure success using completed software. Allow teams to self-organize. Fail fast, learn fast Small scale focus Rapid learning cycles Scrum Framework Product owner prioritizes a backlog of work for the team to do. Every 2 weeks or so, the team looks at the backlog and decides what work can be done next. Team develops and tests solutions until they're done and ready for use. At the end of the 2 weeks the team demonstrates their accomplishments to the product owner and skateholders. Finallt team reflects on how it can improve.