SUMMARIZING OUR MODELS TO DATE 1 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 3 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 Goal Reason who? what? functionality/feature why? value adding As a sales rep I want to view a list of customers so that I can pick one to contact. 4 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 As a sales rep, I want to view a list of customers so that I can pick one to contact. 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. 5 USE CASES VS USER STORIES Customer
Doctor Use Case User Story View Customer List As a sales rep, I want to view a list of customers so that I can pick one to contact. View Patient Prescriptions As a doctor, I want to view a patients prescriptions so that I can look for drug to drug interactions. 6 USE CASES VS USER STORIES DESCRIBING EACH Use Case
User Story View Customer List As a sales rep, I want to view a list of customers so that I can pick one to contact. Use Case Description Acceptance Criteria Customer 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.
7 SCRUM An iterative and incremental agile software development methodology. Frequent releases in short development cycles: 2 to 4-week sprints Product Backlog Sprint Backlog Sprint Planning Increment Sprint Execution Daily Scrum (Stand-up) Task Board
Sprint Review (Demo) Sprint Retrospective + Stakeholders Burn Down Chart 8 SCRUM ROLES Product Owner 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 9 SCRUM MEETINGS Sprint Planning 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. 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) Dev Team gets to say if there are details lacking in the user stories & cannot commit to certain stories 4 hours - inspect & adapt the product; add new items to product backlog Attended by: Product Owner, Dev Team, Scrum Master PLUS: stakeholders Attended by: Product Owner, Dev Team, Scrum Master Sprint Retrospective
3-hours - Process improvement lessons learned, successes & failure Attended by: Scrum Master, Dev Team 10 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. 11 EFFORT ESTIMATION STORY POINTS Fibonacci Sequence: 1, 2, 3, 5, 8, 13 - The sum of the 2 numbers to the left. User Story A 0 1 1 2 3 5 8 13 21 34 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)? T-Shirt Sizing: S, M, L, XL 12 SCRUM ARTIFACTS Product 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 13 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. 14 Task Board User Story As a Sales Rep, I want to view a list of customers so that I can pick one to contact. To Do In Progress 4. Design the UIs 5. Test the
UIs Done 2. Modify the Domain CD 1.Review the User Story details 3. Create a sketch of the UIs As a Sales Rep, I need to maintain client data & locations so that we can properly determine their product needs based on their profile. 3. Create a sketch of the UIs
4. Design the UIs 2. Modify the Domain CD 1.Review the User Story details 5. Test the UIs 15 BURNDOWN CHART Sprint Burndown Chart Assess how much work has been completed Story Points Used by Scrum Masters at the Daily Scrum & Sprint Retrospective meetings
16 STORY MAP Useful when we have so many user stories and we need to understand how to progress through them. 17
