Copyright Intertech, Inc All Rights Reserved. May 18, 2011

Transcription

1 Copyright Intertech, Inc All Rights Reserved. May 18, 2011

2 About Me Dave Schueck Principal Consultant Intertech 20 years experience Variety of technologies, roles, systems, industries Award winning applications Fishing and hunting evangelist Copyright Intertech, Inc Slide 2

3 Agenda The Project Scrum Concepts & Implementation with VS Scrum Template Template customizations Custom artifacts and queries Our Process Steps What do we do at the beginning of a Sprint? What do we do throughout the Sprint? What do we do at the end of the Sprint? Scrum and Waterfall Comparison Mapping of Project Manager duties to Scrum roles Copyright Intertech, Inc Slide 3

4 The Project State Government Case Management System to track client activity in employment and training programs Legacy Written in classic ASP in 2001 Thousands of pages, stored procedures, etc. Thousands of users Waterfall Rewrite Complete system overhaul database, architecture, UI, reports, etc. TFS 2010 Visual Studio Scrum Template Source control, work items, queries, reports, automated builds Copyright Intertech, Inc Slide 4

5 Scrum Overview Methodology / management framework Practices and rules that support empirical process control Transparency, Inspection, Adaptation Self-organizing teams Heavy on communication Provides structure for roles, ceremonies/meetings, and artifacts Adapt and hybridize Copyright Intertech, Inc Slide 5

6 Scrum Overview at 50,000 feet Copyright Intertech, Inc Slide 6

7 Scrum Overview The Process Copyright Intertech, Inc Slide 7

8 Scrum Overview VS Scrum Template Work Item Types Bug Impediment Product Backlog Item Shared Steps Sprint Task Test Case Queries All Sprints Blocked Tasks Open Impediments Product Backlog Sprint Backlog Test Cases Unfinished Work Work in Progress Reports Build Success Over Time Build Summary Release Burndown Sprint Burndown Test Case Progress Test Case Readiness Velocity Copyright Intertech, Inc Slide 8

9 Scrum Basics Sprint Scrum activities are time-boxed to a Sprint Usually 2-4 weeks each Results in demonstrable / potentially shippable product Working software Published documentation Etc. Copyright Intertech, Inc Slide 9

10 Scrum Basics Sprint Our project is doing 4 week Sprints Set the dates on the Sprint work item to one day prior to start, one day after end, such that reports are accurate No template customizations Copyright Intertech, Inc Slide 10

11 Scrum Basics Velocity Measure of a Team s ability to deliver in a Sprint Calculated by average Effort completed through all Sprints Our project is using standard TFS Velocity report No template customizations Copyright Intertech, Inc Slide 11

12 Scrum Roles Committed Pigs Product Owner The Team ScrumMaster Involved Chickens Stakeholders Customers / Users Vendors Managers Legislators Committees Copyright Intertech, Inc Slide 12

13 Scrum Roles Product Owner Responsible for Ensuring product success Establishing and achieving product vision Creating and maintaining Product Backlog Obtaining answers to product requirements questions Considers Stakeholder interests ( voice of the customer ) Decides Sprint acceptance/rejection, or product acceptance/rejection Readiness to ship product Feasibility to continue developing product Not allowed to Be the Scrum Master Copyright Intertech, Inc Slide 13

14 Scrum Roles The Team Responsible for Self-organizing and selfmanaging Negotiating commitments with Product Owner Collaborating with anyone necessary to get the job done Delivering the product Decides Implementation details Considers Stakeholder interests Commitments made to Product Owner Not allowed to Be the Product Owner Copyright Intertech, Inc Slide 14

15 Scrum Roles ScrumMaster Responsible for Facilitating and enforcing the Scrum process Helping the Team Capturing empirical data Considers Stakeholder interests Commitments made to Product Owner Decides An environment that is conducive to the team and process Implementation details Not allowed to Be the Product Owner Copyright Intertech, Inc Slide 15

16 Scrum Roles Our Project Product Owner = Annie ScrumMaster = Dave Team = 16 people Business analysts, developers, DBA Knowingly breaking the best practice for Team size Most Team members are only allocated part-time Copyright Intertech, Inc Slide 16

17 Scrum Artifacts Product Backlog Sprint Backlog Product Backlog Item Sprint Backlog Item (Task) Release Burndown Sprint Burndown Copyright Intertech, Inc Slide 17

18 Scrum Artifacts Definitions Acceptance Criteria Describes the criteria and business rules that must be fulfilled for the given item to be considered done (e.g., user story) Priority Importance of an item relative to other backlog items or tasks We use increments of 5 for priority to make it easier to add/update throughout the Sprint Our project requires acceptance criteria for all backlog items Copyright Intertech, Inc Slide 18

19 Scrum Artifacts Definitions Effort Relative effort required for team to deliver a specific backlog item (e.g., story points) Team consensus achieved through Planning Poker (or similar approach) Use consistent approach throughout the release The Team decided to use a relative effort of High, Medium, Low High = 3 points Medium = 2 points Low = 1 point Copyright Intertech, Inc Slide 19

20 Scrum Artifacts Product Backlog Records a prioritized list of everything that might be needed in the product (i.e., the requirements) Responsible Party Product Owner Characteristics Never complete Includes features, bugs, R&D, etc. Contains Product Backlog Items Sorted in priority order Lower priority items contain less detail Copyright Intertech, Inc Slide 20

21 Scrum Artifacts Product Backlog Our project uses customized Product Backlog query Using Under prevents backlog items from dropping into a black hole (i.e., any item that isn t associated with the root iteration) Copyright Intertech, Inc Slide 21

22 Scrum Artifacts Product Backlog View/edit in TFS or Excel Copyright Intertech, Inc Slide 22

23 Copyright Intertech, Inc Slide 23

24 Scrum Artifacts Product Backlog View/edit in Telerik TFS Work Item Manager Copyright Intertech, Inc Slide 24

25 Scrum Artifacts Sprint Backlog Records a list of tasks to complete a set of Product Backlog items, thereby resulting in a done increment Responsible Party Team Characteristics Complete / empty when the Sprint is finished Contains Sprint Backlog Items Updated daily at a minimum Feeds the Sprint Burndown Copyright Intertech, Inc Slide 25

26 Scrum Artifacts Sprint Backlog Our project uses customized Sprint Backlog query Added another clause to the linked work items query Copyright Intertech, Inc Slide 26

27 Scrum Artifacts Sprint Backlog View/edit in TFS or Excel Copyright Intertech, Inc Slide 27

28 Copyright Intertech, Inc Slide 28

29 Scrum Artifacts Sprint Backlog View/edit in another tool Telerik TFS Work Item Manager AIT TeamSystemPro Task Board EMC TFS Workbench Urban Turtle Copyright Intertech, Inc Slide 29

30 Telerik TFS Work Item Manager Copyright Intertech, Inc Slide 30

31 AIT TeamSystemPro Task Board Copyright Intertech, Inc Slide 31

32 EMC TFS Workbench Copyright Intertech, Inc Slide 32

33 Urban Turtle Copyright Intertech, Inc Slide 33

34 Scrum Artifacts Product Backlog Item (PBI) Specifies a requirement for the product Responsible Party Product Owner Characteristics User Stories Epics (i.e., large user stories, or groups of stories) Non-functional or technical requirements Spikes Bugs Copyright Intertech, Inc Slide 34

35 Scrum Artifacts More on PBI s User Story Describes something of business value in 1 sentence Typically authored by Product Owner (or designate) As a <type of user> I want to <some goal> so that <some reason> Also includes Acceptance Criteria, Priority, and Effort Spike Investigative User Story need to learn more, report findings, POC R&D, tool evaluation, or prototyping Bug investigation Process improvement Copyright Intertech, Inc Slide 35

36 Scrum Artifacts PBI Our project uses customized PBI template Moved fields Copyright Intertech, Inc Slide 36

37 Scrum Artifacts PBI Team standards for PBI Prefixes for Title <user role>, ANALYSIS, DEBT, EPIC, NFR, SPIKE E.g., Security Administrator Add Access Group E.g., DEBT Pay down design and technical debt for Sprint 4 E.g., NFR Establish coding standards User story Description must contain <some reason> Description for non-functional requirements should try the standard story format, if possible Acceptance Criteria are required and includes business rules Copyright Intertech, Inc Slide 37

38 Scrum Artifacts Bug Our project uses customized Bug template Moved fields Copyright Intertech, Inc Slide 38

39 Scrum Artifacts Sprint Backlog Item (Task) Specifies a task for a Sprint Responsible Party Team Characteristics Effort usually = 3 days or less Tasks include anything in the spectrum for software engineering Installation & configuration, infrastructure, coding, documentation, testing, training, etc. Copyright Intertech, Inc Slide 39

40 Scrum Artifacts Sprint Backlog Item (Task) Our project uses customized Task template Moved fields & Added field Copyright Intertech, Inc Slide 40

41 Scrum Artifacts Sprint Backlog Item (Task) Team standards for Task Link related tasks Tasks are duplicated if multiple people are working together on an activity We have a standard set of tasks that are considered during every Sprint Planning meeting Copyright Intertech, Inc Slide 41

42 Scrum Artifacts Release Burndown Measures remaining Product Backlog across the time of a release plan Responsible Party Product Owner Characteristics Chart with an optional trend line Complete when all Sprints are complete Copyright Intertech, Inc Slide 42

43 Scrum Artifacts Release Burndown Our project is using standard Release Burndown report No template customizations With our type of project, the product backlog takes time to build Copyright Intertech, Inc Slide 43

44 Scrum Artifacts Sprint Burndown Measures remaining Sprint Backlog across the time of a Sprint Responsible Party ScrumMaster Characteristics Graph with trend line Updated daily Complete when the Sprint is complete Copyright Intertech, Inc Slide 44

45 Scrum Artifacts Sprint Burndown Our project is using standard Sprint Burndown report No template customizations Refreshed every 2 hours, and 8:00 a.m. daily Copyright Intertech, Inc Slide 45

46 Custom Artifacts Still dipping a couple of our toes in the water(fall) for various reasons Change Request (adapted from MSF CMMI template) Communication (custom) Risk (adapted from MSF CMMI template) Specification (custom) Copyright Intertech, Inc Slide 46

47 Custom Artifacts Change Request Enforces traceability to formal change requests that customers can make Copyright Intertech, Inc Slide 47

48 Custom Artifacts Communication Enables Product Owner to measure communication plan goals vs. actual Copyright Intertech, Inc Slide 48

49 Custom Artifacts Risk Enables us to produce a formal risk report required by another state agency Copyright Intertech, Inc Slide 49

50 Scrum Ceremonies Sprint Planning Daily Scrum Sprint Review Sprint Retrospective Copyright Intertech, Inc Slide 50

51 Scrum Ceremonies Sprint Planning Establish the scope for a Sprint, and how the scope will be delivered Attendees: Product Owner, ScrumMaster, Team 2 to 6 hours Agenda Part 1 Define what will be committed to Inputs: Product Backlog, latest increment of the product, team velocity, and team schedule for Sprint Outputs: PBI s committed to, relative effort for each PBI, Sprint goal, Sprint start/end dates Part 2 Define how the committed items will be completed (i.e., tasks) Inputs: Results of part 1 Outputs: prioritized set of tasks and test cases that correlate to PBI s, effort for each task Copyright Intertech, Inc Slide 51

52 Scrum Ceremonies Sprint Planning We use the following: Ceiling projector, whiteboard, paper, TFS, Velocity report, team calendar Copyright Intertech, Inc Slide 52

53 Scrum Ceremonies Sprint Planning We use the Iteration Planning Tool in Telerik TFS Work Item Manager Copyright Intertech, Inc Slide 53

54 Scrum Ceremonies Daily Scrum Improve communications, identify impediments to progress, highlight and promote quick decision-making, and improve everyone's level of project knowledge Attendees: Product Owner, ScrumMaster, Team 15 minutes Agenda What did I accomplish yesterday? What do I plan to accomplish today? What obstacles are in my way? Rules Stand up Speak briefly; Chickens cannot speak or interfere Don t attempt to solve obstacles in the meeting Copyright Intertech, Inc Slide 54

55 Scrum Ceremonies Daily Scrum 8:45 a.m. Focus on: What do I plan to accomplish today? What obstacles are in my way? We use the following: Sprint Backlog Sprint Burndown Copyright Intertech, Inc Slide 55

56 Scrum Ceremonies Sprint Review Collaborate about what was completed during the Sprint, and about what could be done during the next Sprint Attendees: Product Owner, ScrumMaster, Team, stakeholders, users, any interested parties 1 to 3 hours Agenda What was done / not done during the Sprint? Demonstration of work completed Discuss questions and feedback pertaining to what was demonstrated Provide brief overall status of Product Backlog Discuss functionality that could possibly be done in the next Sprint Copyright Intertech, Inc Slide 56

57 Scrum Ceremonies Sprint Review 1 day after the Sprint ends We use the following: WebEx Working software Notes entered directly into TFS Copyright Intertech, Inc Slide 57

58 Scrum Ceremonies Sprint Retrospective Inspect the last Sprint in regards to people, relationships, process, tools, etc. Identify improvements. Attendees: Product Owner, ScrumMaster, Team 1 to 2 hours Agenda What worked well? What didn t work well? What should be changed to make the next Sprint more effective and enjoyable? Copyright Intertech, Inc Slide 58

59 Scrum Ceremonies Sprint Retrospective 1 or 2 days after the Sprint ends We use the following: Notes entered directly into TFS Copyright Intertech, Inc Slide 59

60 Custom Queries A series of queries for the All dimension E.g., All User Stories My Sprint Backlog Unfinished Tasks with No Remaining Work Unlinked Tasks User Stories without Test Cases Copyright Intertech, Inc Slide 60

61 Custom Queries My Sprint Backlog Lists all PBI s, bugs, and their linked tasks that are assigned to a team member to complete in the current sprint Copyright Intertech, Inc Slide 61

62 Custom Queries Unfinished Tasks with No Remaining Work Identifies tasks that should either be changed to Done status, or should contain some Remaining Hours Copyright Intertech, Inc Slide 62

63 Custom Queries Unlinked Tasks Identifies tasks that are not linked to any other work item type (i.e., not linked to user story, test case, etc.) need to ask why these exist Copyright Intertech, Inc Slide 63

64 Custom Queries User Stories without Test Cases Identifies user stories for which test cases need to be written Copyright Intertech, Inc Slide 64

65 Our Process Steps What do we do at the beginning of a Sprint? 1. ScrumMaster ensure that an iteration exists for the Sprint. If none exists, then add one. 2. ScrumMaster modify the Current Sprint and Custom queries to pull from the proper iteration 3. ScrumMaster, Team, Product Owner prepare for and execute the Sprint Planning meeting a) ScrumMaster add or update the Sprint work item b) ScrumMaster edit the Product Backlog Items and Bugs c) ScrumMaster add tasks to TFS 4. ScrumMaster verify that the Sprint Backlog query returns the appropriate results 5. ScrumMaster calculate the task assigned hours per person. Compare those metrics to staff capacity and adjust as needed. 6. ScrumMaster send an to the Product Owner and Team summarizing the commitments for the given Sprint 7. ScrumMaster save the Sprint assets Copyright Intertech, Inc Slide 65

66 Our Process Steps What do we do throughout the Sprint? 1. Team create and link work items, as needed 2. Team work on and complete tasks in the order specified by the backlog priority a) When you start a task, set the state to In Progress b) Update daily the remaining work estimate on your in-progress tasks c) Complete your work according to the acceptance criteria defined in the Product Backlog Items and Bugs d) When you complete a task, set the state to Done and remaining work to 0 3. Team if you are done with your tasks, then see if you can take ownership of other tasks 4. Team add, edit, and resolve Impediment work items as needed 5. ScrumMaster review the Sprint Backlog and Sprint Burndown to monitor progress daily Copyright Intertech, Inc Slide 66

67 Our Process Steps What do we do at the end of the Sprint? 1. Product Owner review all Product Backlog Items and Bugs on the Sprint Backlog, and verify that Acceptance Criteria has been met 2. ScrumMaster, Product Owner update Product Backlog Items and Bugs, as needed, to reflect accepted vs. not accepted 3. ScrumMaster, Product Owner add Product Backlog Items and Bugs as needed 4. ScrumMaster, Product Owner execute the Sprint Review meeting 5. ScrumMaster execute the Sprint Retrospective meeting Copyright Intertech, Inc Slide 67

68 Our Process Steps What do we do at the end of the Sprint? 6. ScrumMaster update all incomplete tasks at the end of a Sprint a) Change the State to Removed b) Set the Reason to Unfinished at end of Sprint 7. ScrumMaster, Product Owner update product backlog items that contained incomplete tasks at the end of a Sprint a) Change the State to Approved b) Change the Iteration to something other than the Sprint you just finished 8. ScrumMaster save more Sprint assets 9. Team celebrate Copyright Intertech, Inc Slide 68

69 Scrum and Waterfall Comparison Concept Waterfall Scrum Engineering Lifecycle Overall Lifecycle Sequence of stages/phases with milestones that are gated. Stages usually correlate with planning, analysis & requirements, development, testing, and deployment. Each stage is dependent on the full completion of the last stage. Process Control Defined process control every aspect of the project is planned, defined, and documented, usually with sign-offs. Sequence of iterations (i.e., sprints), where each iteration may contain aspects of all stages. Empirical process control only those project assets that are deemed necessary are the ones that are created. Controlled by frequent inspection and adaptation. Copyright Intertech, Inc Slide 69

70 Scrum and Waterfall Comparison Concept Waterfall Scrum Engineering Phases Business Analysis and Requirements SRS, use cases User stories, epics, possibly use cases Construction Source code, database, scripts, etc. Source code, database, scripts, etc. Deployment Deployment steps, operations manual, build scripts, etc. Build scripts, automated builds & deployments Testing Test cases, test scripts, test execution log User story acceptance criteria, test cases, test scripts, test execution log favors all of these as executable / automated Copyright Intertech, Inc Slide 70

71 Scrum and Waterfall Comparison Concept Waterfall Scrum Meetings Iteration Planning Meetings Iteration Review Meetings Post-mortem Meeting Status Meetings None Sprint planning meetings to define work items and estimates for the iteration, usually held monthly. Milestone review meetings Sprint review meetings to demonstrate results of the sprint, usually held monthly. Lessons learned meeting, usually held at the end of the project. Agenda usually focuses on what went well, and what needs improvement on next project. Team status meeting, usually held weekly with varying agenda. Meeting length = varies (but often 1 hour). Sprint retrospective meeting held at completion of each sprint. Agenda focuses on what went well, what needs improvement, and which items will be acted upon in the next sprint. Daily Scrum meetings where team members answer 3 questions. Meeting length = 15 minutes. Copyright Intertech, Inc Slide 71

72 Scrum and Waterfall Comparison Concept Waterfall Scrum Product Management Product Ownership Varies Single product owner (preferably) Product Releases Product usually delivered as a whole at the end Product delivered incrementally Copyright Intertech, Inc Slide 72

73 Scrum and Waterfall Comparison Concept Waterfall Scrum Project Management Change Management Create a process for requesting, approving, and prioritizing changes. Focus for approval and prioritization should be on the business (i.e., product owner). Issue Management Issue log Impediment list Management Structure Hierarchical structure, often silo groups Create a process for requesting, approving, and prioritizing changes. Focus for approval and prioritization should be on the business (i.e., product owner). Flat, team structure Project Tracking Project status, schedule, Gantt chart Release burndown, sprint burndown Risk Management Risk management plan Anticipated impediment list Copyright Intertech, Inc Slide 73

74 Scrum and Waterfall Comparison Concept Waterfall Scrum Project Management Scope Management High level feature list, work breakdown structure Stress Management Varies Varies Timeline Checkpoints Milestone Product backlog, sprint backlog Sprint review Work Estimates Time estimates (e.g., man hours) Relative work estimates (e.g., story points) Work Item Task Sprint backlog item Copyright Intertech, Inc Slide 74

75 Mapping of PM Duties to Scrum Roles Category or Knowledge Area Expectation Management Expectation Management Expectation Management Expectation Management Expectation Management Expectation Management Expectation Management Expectation Management Expectation Management PMBOK Process Groups Duty Product Owner Scrum Master Executing Facilitates Meetings X Planning Align Project with Corporate Strategy X Planning, Executing Communicate X X X Team Planning, Executing Communicate with Management and Executives X X Planning, Executing Follow Up with Team and Stakeholders X X X Planning, Executing Identify and Manage Stakeholders X Planning, Executing Identify Constraints and Assumptions X Planning, Executing Interact with Users X X Planning, Executing Interface with Project Management Office X Other Copyright Intertech, Inc Slide 75

76 Mapping of PM Duties to Scrum Roles Category or Knowledge Area Integration Management Integration Management PMBOK Process Groups Planning, Executing Duty Manage Administrative Integration with Other Projects Product Owner Scrum Master Planning, Executing Manage Technical Integration with Other Projects X X X Team Other Project Closure Closing Evaluate Project Results X Project Closure Closing Lessons Learned X Project Planning Initiating Project Charter X X X Project Planning Planning Establish and Communicate Project Goals X Project Planning Planning Planning X X Copyright Intertech, Inc Slide 76

77 Mapping of PM Duties to Scrum Roles Category or Knowledge Area PMBOK Process Groups Duty Product Owner Scrum Master Team Other Project Tracking Executing Monitor Project (daily) X Project Tracking Executing Report Project Status X X Project Tracking Executing Report Task Status X X Project Tracking Planning, Executing Estimate Costs X X Project Tracking Planning, Executing Locate and Secure Funding X X Project Tracking Planning, Executing Manage Budget X X X Project Tracking Planning, Executing Manage Contractual Relationships X Project Tracking Planning, Executing Manage Long-Term Schedule X X Project Tracking Planning, Executing Manage Short-Term Schedule X X Copyright Intertech, Inc Slide 77

78 Mapping of PM Duties to Scrum Roles Category or Knowledge Area Quality Management Quality Management Quality Management Resource Management Resource Management Resource Management PMBOK Process Groups Duty Product Owner Scrum Master Planning, Executing Enforce Corporate Policies X Planning, Executing Enforce Process and Standards X Planning, Executing Manage Quality X X Team Executing Supervise Staff X Planning, Executing Balance Staff Assignments to Capacity X Planning, Executing Choose Staff X Other Risk Management Planning, Executing Escalate Issues X Risk Management Planning, Executing Identify Obstacles X X X Risk Management Planning, Executing Manage Risk X X X Copyright Intertech, Inc Slide 78

79 Mapping of PM Duties to Scrum Roles Category or Knowledge Area PMBOK Process Groups Duty Product Owner Scrum Master Team Other Scope Management Initiating, Planning, Executing Manage Scope X Scope Management Planning Analyze Requirements X X Scope Management Planning, Executing Approve Requirements / Features X Scope Management Planning, Executing Assign Tasks X X Scope Management Planning, Executing Estimation of Requirements X Scope Management Planning, Executing Estimation of Tasks X Scope Management Planning, Executing Obtain Requirements / Features X Scope Management Planning, Executing Prioritize Requirements / Features X Scope Management Planning, Executing Prioritize Tasks X X Copyright Intertech, Inc Slide 79

80 Mapping of PM Duties to Scrum Roles Category or Knowledge Area PMBOK Process Groups Duty Product Owner Scrum Master Team Other Stress Management Executing Celebrate Success X X X Stress Management Executing Remove Obstacles X X Stress Management Executing Resolve Conflict X Copyright Intertech, Inc Slide 80

81 Wrap-up Visual Studio 1.0 Scrum Template df be cbfc5d8e Contact Info Copyright Intertech, Inc Slide 81

82 Thank You Copyright Intertech, Inc Slide 82