1. SWE 3613 SCRUM Practices (Chapter 3 of your Text)

2. Some Major Components Product Owner SCRUM Master Product Backlog SCRUM TEAM

3. Product Backlog and Product Owner • Product Backlog : • Anything that represents work to be done is included • A prioritized list of requirements and tasks • May be reprioritized and evolving but is always “visible” • Initially empty, but when enough to drive a SPRINT ---triggers a SPRINT • Developed from sales/marketing; customers; support; etc. • Product Owner: • Responsible for, manages and controls the Backlog • Together with developers, QA and managers estimate the effort for developing each backlog (dangerous) • Clarifies and redefines the backlog item, if unclear

4. SCRUM Team • Developers who “commits” to achieving the SPRINTGoal: • People of different skills and strength • Each team is usually about 5-9 (7 +or- 2)members in size • Should have at least one experienced person • Some may be part-time for special skills • Must possess all the necessary skills needed to perform the SPRINT • There may be several SCRUM teams running separate SPRINT in parallel ---- but they have minimal dependence • The team decides on the # of and type of backlog items to include in each SPRINT. • Decides on how to perform the tasks and meet the goal • Use “open” work environment that encourages joint-work.(loners need to change theirs attitude/work habit to fit the team.) • Can cancel a SPRINT ----- very rarely happens • Works very closely with the SCRUM Master

5. SCRUM Master • A new type of project manager who ensures that SCRUM values, practices and rules are enforced • Listens to SCRUM team members and gauges the progress made towards the SPRINT goal. • Runs the Daily Scrum Meetings • Works with the customers and management to institute and identify a Product Manager. • Makes decisions (has the authority to): • Removes impediments • Ensures needed tools, infrastructure, etc. are available • Must have the “personality, skills, and knowledge” suited to be able to perform the role. • Integrity and courageous • Persistent • Detail oriented • Competent

6. Daily SCRUM Meetings • “Daily” SCRUM meeting is a short (15-20 minutes) meeting conducted for communicating the projectstatus by describing: • What has been accomplished since the last meeting • What is going to be done before the next meeting • What obstacles are in the way that need to be removed These meetings are: “team” based; rapid; cooperative; intense; courteous; decisive

7. More on Daily SCRUM Meetings • SCRUM Master is responsible for successfully running these meetings: • Enforcing the rules: starting on time; everyone participates; everyone speaks briefly; meeting ends on time • Time and Location of the meeting should be consistent, with possibly a “dedicated SCRUM-Room” • The meeting should be “daily”; then the short interval allows a better and easier “continuous” project monitoring • The SCRUM team membersare considered a “committed” and often referred to as “PIGS” may speak. All others are considered as “Chickens” and are observers. (Comes from a joke about the breakfast of “Ham and Eggs”)

8. More on Daily SCRUM Meetings (cont.) • Remember that this is NOT a problem solving meeting, but a status meeting. So, “PIGS” are expected to answer 3 questions: • What have you accomplished since last meeting? • What will you do next between now and next meeting? • What, if anything, is in your way of doing your work ? • If there is an impediment, SCRUM Master must record it and “remove” the problem: • Lack of tools, knowledge or needed artifacts • Too much interruptions • Possibly personal problems, etc. • If the impediment can not be resolved ---- the SPRINT may be canceled!

9. Establishing “Follow-UP Problem Solving” • Problem solving is NOT performed during the “Daily” SCRUM meeting, ---but at “follow-up” Working Sessions afterwards: • May include members outside of the SCRUM team for this SPRINT • The SCRUM Team has the “full” authority to make all the decisions concerning the SPRINT, including the cancellation of the SPRINT