Summarizing Our Models to Date

Analysis – Requirements Model Traditional Analysis Models Data Flow Diagrams ERD Object-Oriented Analysis Models - UML Use Case Diagram Domain Class Diagram Use Case Descriptions Activity Diagrams

Scrum

User Story (def) a high-level description of a requirement (i.e. functionality) that is valuable to a user or product owner of the software product. User Role – who? Goal – what? functionality/feature Reason – why? value adding As a sales rep I want to view a list of customers so that I can pick one to contact.

Acceptance Criteria Acceptance criteria provide clarity as to the expectation. Contains 3 to 5 functional criteria regarding the user story what the user must be able to do what the user must not be able to do what the system must do User Story Acceptance Criteria As a sales rep, I want to view a list of customers so that I can pick one to contact. Display all customer info by customer ID in tabular form. Include filtering & sorting. Show total records & total visible records. Accessible from the main navigation menu.

Use Cases vs User Stories User Story As a sales rep, I want to view a list of customers so that I can pick one to contact. Customer View Customer List As a doctor, I want to view a patient’s prescriptions so that I can look for drug to drug interactions. Doctor View Patient Prescriptions

Use Cases vs User Stories – Describing Each User Story As a sales rep, I want to view a list of customers so that I can pick one to contact. View Customer List Customer Use Case Description Acceptance Criteria Display all customer info by customer ID in tabular form. Include filtering & sorting. Show total records & total visible records. Accessible from the main navigation menu.

Scrum Sprint Execution Product Backlog Sprint Backlog Increment An iterative and incremental agile software development methodology. Frequent releases in short development cycles: 2 to 4-week sprints Product Backlog Sprint Backlog Increment Sprint Execution Sprint Review (“Demo”) Sprint Planning Sprint Retrospective Daily Scrum (“Stand-up”) + Stakeholders Task Board Burn Down Chart

Scrum Roles Product Owner Scrum Master Development Team client stakeholder who controls the Product Backlog Scrum Master a facilitator removes impediments, resolves issues Development Team 5-9 members Cross-functional skills “the developers” self-organizing teams complete control over organization & work processes They decide what goes in a Sprint

Scrum Meetings Sprint Planning Daily Scrum (“Stand-Up”) 8 hours - Creating the Sprint Backlog Part I: Product Owner presents the desired User Stories & the acceptance criteria for each story. Part II: Dev Team identifies tasks for each story; creates time estimates per task; finalizes the user stories they can commit to. Dev Team gets to say if there are details lacking in the user stories & cannot commit to certain stories Attended by: Product Owner, Dev Team, Scrum Master Daily Scrum (“Stand-Up”) 15 mins daily – Status update w/in dev team Yesterday, Today, Barriers Attended by: Development Team, Scrum Master Sprint Review (“Demo”) 4 hours - inspect & adapt the product; add new items to product backlog Attended by: Product Owner, Dev Team, Scrum Master PLUS: stakeholders Sprint Retrospective 3-hours - Process improvement lessons learned, successes & failure Attended by: Scrum Master, Dev Team

Epic - a large Backlog item Scrum Meetings Backlog Refinement – “Grooming” Refining the next items on the product backlog to prepare for the next sprint(s). It includes: Clarifying backlog items Reducing Epics into smaller items Determining dependencies Task can be done during a Sprint Planning Meeting but many prefer to do this in a separate meeting (e.g. toward the end of a sprint). Epic - a large Backlog item An Epic is a feature that is too broad/complex to be completed in 1 sprint and should be split into multiple stories.

Effort Estimation – Story Points Fibonacci Sequence: 1, 2, 3, 5, 8, 13 - The sum of the 2 numbers to the left. T-Shirt Sizing: S, M, L, XL 0 1 1 2 3 5 8 13 21 34 User Story A Assume: User Story B is about half the difficulty of User Story A. With Fibonacci, you will never see half of any number! It forces you to think! Is this user story a little more difficult than half (i.e. 5)?, or Is it a little less difficult than half (i.e. 3)?

Scrum Artifacts Product Backlog Increment Task Board Sprint Backlog Product Owner Prioritized List of Product Backlog Items (PBIs) PBIs are written as user stories and will have: Acceptance Criteria Story Points/Effort Estimated – by dev team Increment Potentially Shippable Product or Potentially Deployable Product Product Owner decides when to release Task Board For each item in the Sprint Backlog, list & classify all tasks: To Do, In Progress, Done Sprint Backlog Development Team List of PBIs committed to Includes the Tasks for each PBI Sprint Burndown Chart Shows amount of work remaining in one sprint

Taskboard A quick visual way for everyone to see how the project is going. It is the focal point during the Daily Scrum. Task Board User Story To Do In Progress Done As a Sales Rep, I want to view a list of customers so that I can pick one to contact. As a Sales Rep, I need to maintain client data & locations so that we can properly determine their product needs based on their profile.

User Story To Do In Progress Done Task Board User Story To Do In Progress Done As a Sales Rep, I want to view a list of customers so that I can pick one to contact. As a Sales Rep, I need to maintain client data & locations so that we can properly determine their product needs based on their profile. 4. Design the UIs 2. Modify the Domain CD 1.Review the User Story details 5. Test the UIs 3. Create a sketch of the UIs 3. Create a sketch of the UIs 2. Modify the Domain CD 1.Review the User Story details 5. Test the UIs 4. Design the UIs

Burndown Chart Sprint Burndown Chart Assess how much work has been completed Used by Scrum Masters at the Daily Scrum & Sprint Retrospective meetings Story Points

Story Map Useful when we have so many user stories and we need to understand how to progress through them.