This document provides an introduction to agile planning and project management. It defines key concepts like projects, project managers, and project management. It discusses the agile manifesto and values like individuals and interactions, working software, customer collaboration, and responding to change. It also covers agile processes like product vision, product backlog, iteration backlog, and feedback loops. The document discusses when agile is a good fit and compares predictive and empirical processes. It outlines fundamentals of team-based agile like roles, estimating techniques like story points, and managing the delivery process.
COMPUTER 10: Lesson 7 - File Storage and Online Collaboration
Agile Project Management
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
11.
12.
13.
14.
15.
16.
17.
18.
19.
20.
21.
22.
23.
24.
25.
26.
27.
28.
29.
30.
31.
32.
33.
34.
35.
36.
37.
38.
39.
40.
41.
42.
43.
44.
45.
46.
47.
48.
49.
50.
51.
52.
53.
54.
55.
56.
57.
58.
59.
60.
61.
62.
63.
64.
65.
66.
67.
68.
69.
70.
71.
72.
73.
74.
75.
76.
77.
78.
79.
80.
81.
82.
83.
84.
85.
86.
87.
88.
89.
90.
91.
92.
93.
94.
95.
96.
97.
98.
99.
100.
101.
102.
103.
104.
105.
106.
107.
108.
109.
110.
111.
112.
113.
114.
115.
116.
117.
118.
119.
120.
121.
122.
123.
124.
125.
126.
127.
128.
129.
130.
131.
132.
133.
134.
135.
136.
137.
138.
139.
140.
141.
142.
143.
144.
145.
146.
147.
148.
149.
150.
151.
152.
153.
154.
155.
156.
157.
158.
159.
160.
161.
162.
163.
164.
165.
166.
167.
168.
169.
170.
171.
172.
173.
174.
175.
176.
177.
178.
179.
180.
181.
182.
183.
184.
185.
186.
187.
188.
189.
190.
191.
192.
193.
194.
195.
196.
197.
198.
199.
200.
201.
202.
203.
204.
205.
206.
207.
208.
Notas del editor
So, before we get started, a little about me. My name is Mike Cottmeyer, I am an agile transformation coach with Pillar technology. Before I joined Pillar I was a trainer and consultant with VersionOne. Before that I ran a pretty large agile portfolio of projects for CheckFree (now Fiserv). Pillar Technology has been around for about 13 years and is just about 100 people strong. Pillar specializes in agile transformation and project delivery. We can bring in agile coaches on the leadership and project management side. We can bring in coaches to help you with TDD. We can spin up teams and help you deliver projects.
Scrum is a team based methodology…Ideal team size is 5 to 9 peopleTeam has everything it needs to deliver an increment of working productVery clear role and responsibility delineation: ScrumMaster, Product Owner, TeamProduct Owner brings the whatTeam decides the howWIP is limited by the velocity of the teamScrumMaster’s job is to get rid of the stuff slowing the team down The idea is to deliver in short sprints…… use empirical process control, inspect and adaptTotally designed to be a lightweight framework for delivering products in the face of uncertaintyI
Scrum is a team based methodology…Ideal team size is 5 to 9 peopleTeam has everything it needs to deliver an increment of working productVery clear role and responsibility delineation: ScrumMaster, Product Owner, TeamProduct Owner brings the whatTeam decides the howWIP is limited by the velocity of the teamScrumMaster’s job is to get rid of the stuff slowing the team down The idea is to deliver in short sprints…… use empirical process control, inspect and adaptTotally designed to be a lightweight framework for delivering products in the face of uncertaintyI
Scrum is a team based methodology…Ideal team size is 5 to 9 peopleTeam has everything it needs to deliver an increment of working productVery clear role and responsibility delineation: ScrumMaster, Product Owner, TeamProduct Owner brings the whatTeam decides the howWIP is limited by the velocity of the teamScrumMaster’s job is to get rid of the stuff slowing the team down The idea is to deliver in short sprints…… use empirical process control, inspect and adaptTotally designed to be a lightweight framework for delivering products in the face of uncertaintyI
Scrum is a team based methodology…Ideal team size is 5 to 9 peopleTeam has everything it needs to deliver an increment of working productVery clear role and responsibility delineation: ScrumMaster, Product Owner, TeamProduct Owner brings the whatTeam decides the howWIP is limited by the velocity of the teamScrumMaster’s job is to get rid of the stuff slowing the team down The idea is to deliver in short sprints…… use empirical process control, inspect and adaptTotally designed to be a lightweight framework for delivering products in the face of uncertaintyI
Scrum is a team based methodology…Ideal team size is 5 to 9 peopleTeam has everything it needs to deliver an increment of working productVery clear role and responsibility delineation: ScrumMaster, Product Owner, TeamProduct Owner brings the whatTeam decides the howWIP is limited by the velocity of the teamScrumMaster’s job is to get rid of the stuff slowing the team down The idea is to deliver in short sprints…… use empirical process control, inspect and adaptTotally designed to be a lightweight framework for delivering products in the face of uncertaintyI
Scrum is a team based methodology…Ideal team size is 5 to 9 peopleTeam has everything it needs to deliver an increment of working productVery clear role and responsibility delineation: ScrumMaster, Product Owner, TeamProduct Owner brings the whatTeam decides the howWIP is limited by the velocity of the teamScrumMaster’s job is to get rid of the stuff slowing the team down The idea is to deliver in short sprints…… use empirical process control, inspect and adaptTotally designed to be a lightweight framework for delivering products in the face of uncertaintyI
Scrum is a team based methodology…Ideal team size is 5 to 9 peopleTeam has everything it needs to deliver an increment of working productVery clear role and responsibility delineation: ScrumMaster, Product Owner, TeamProduct Owner brings the whatTeam decides the howWIP is limited by the velocity of the teamScrumMaster’s job is to get rid of the stuff slowing the team down The idea is to deliver in short sprints…… use empirical process control, inspect and adaptTotally designed to be a lightweight framework for delivering products in the face of uncertaintyI
So here is our small agile team.
Agile teams are cross functional units that have everything they need to deliver some increment of business value. In a software organization… the agile team is going to have one or more developers…
They will have one or more QA testers. Sometimes teams have technical testers that are responsible for writing unit tests… sometimes this is left up to the developers. Sometimes teams have manual testers… possibly exercising the UI. Many teams will do both kinds of testing.
Sometimes a team will someone playing the role of business analyst. This can be a dedicated position on the team… or it might be blended with some other role… maybe a lead developer. Often times teams will have a BA that is serving as a proxy product owner for the real customer or product owner. Dedicated or blended Custome proxy
Agile teams will usually have someone in the role of ScrumMaster or Agile process coordinator. This can be a dedicated position on the team or a role that is shared with another role on the team. Sometimes you have a dedicated ScrumMaster but they are working with more than one agile team at a time.
Last but not least we have a product owner. They are the interface between the team and the business. They are the single wringable neck and responsible for the business outcomes of the product. They define requirements, set the priorties, and othewise help the team converge on the best possible outcome to meet the business objectives. Agile teams have all these roles in some form or fashion… they are self contained and independent. This kind of team is the backdrop to almost everything you read about adopting agile. This is such an important concept because if this isn't’ the kind of team you are building as you adopt agile… some of the things you are learning about just aren’t going to work.
11. We start with high level requirements that become more detailed as we learn more about the product we are building. We start with high level architectural representations that emerge toward detailed design as we actually begin developing the working product. You might think of this as rolling wave planning or progressive elaboration. The idea is that we plan based on what we know, and plan more as we learn more.
12. Our goal is to recognize, that on projects where we have a tremendous amount of uncertainty... we don't want to create plans that don't reflect our current understanding of reality. We don't want to assume the process overhead of change management, when change is going to be the norm. Agile gives us a way to manage our projects, in the face of uncertainty, while aggressively working to reduce risk and uncertainty.
Scrum is a team based methodology…Ideal team size is 5 to 9 peopleTeam has everything it needs to deliver an increment of working productVery clear role and responsibility delineation: ScrumMaster, Product Owner, TeamProduct Owner brings the whatTeam decides the howWIP is limited by the velocity of the teamScrumMaster’s job is to get rid of the stuff slowing the team down The idea is to deliver in short sprints…… use empirical process control, inspect and adaptTotally designed to be a lightweight framework for delivering products in the face of uncertaintyI
Explaining the hierarchy of value
Explaining the hierarchy of value
Explaining the hierarchy of value
Story Mapping
Story Mapping
Story Mapping
Story Mapping
Story Mapping
Story Mapping
Story Mapping
Story Mapping
Story Mapping
Story Mapping
Story Mapping
Story Mapping
Story Mapping
Story Mapping
Story Mapping
Scrum is a team based methodology…Ideal team size is 5 to 9 peopleTeam has everything it needs to deliver an increment of working productVery clear role and responsibility delineation: ScrumMaster, Product Owner, TeamProduct Owner brings the whatTeam decides the howWIP is limited by the velocity of the teamScrumMaster’s job is to get rid of the stuff slowing the team down The idea is to deliver in short sprints…… use empirical process control, inspect and adaptTotally designed to be a lightweight framework for delivering products in the face of uncertaintyI
Story Mapping
Story Mapping
Story Mapping
Story Mapping
Scrum is a team based methodology…Ideal team size is 5 to 9 peopleTeam has everything it needs to deliver an increment of working productVery clear role and responsibility delineation: ScrumMaster, Product Owner, TeamProduct Owner brings the whatTeam decides the howWIP is limited by the velocity of the teamScrumMaster’s job is to get rid of the stuff slowing the team down The idea is to deliver in short sprints…… use empirical process control, inspect and adaptTotally designed to be a lightweight framework for delivering products in the face of uncertaintyI
Scrum is a team based methodology…Ideal team size is 5 to 9 peopleTeam has everything it needs to deliver an increment of working productVery clear role and responsibility delineation: ScrumMaster, Product Owner, TeamProduct Owner brings the whatTeam decides the howWIP is limited by the velocity of the teamScrumMaster’s job is to get rid of the stuff slowing the team down The idea is to deliver in short sprints…… use empirical process control, inspect and adaptTotally designed to be a lightweight framework for delivering products in the face of uncertaintyI
Scrum is a team based methodology…Ideal team size is 5 to 9 peopleTeam has everything it needs to deliver an increment of working productVery clear role and responsibility delineation: ScrumMaster, Product Owner, TeamProduct Owner brings the whatTeam decides the howWIP is limited by the velocity of the teamScrumMaster’s job is to get rid of the stuff slowing the team down The idea is to deliver in short sprints…… use empirical process control, inspect and adaptTotally designed to be a lightweight framework for delivering products in the face of uncertaintyI
Scrum is a team based methodology…Ideal team size is 5 to 9 peopleTeam has everything it needs to deliver an increment of working productVery clear role and responsibility delineation: ScrumMaster, Product Owner, TeamProduct Owner brings the whatTeam decides the howWIP is limited by the velocity of the teamScrumMaster’s job is to get rid of the stuff slowing the team down The idea is to deliver in short sprints…… use empirical process control, inspect and adaptTotally designed to be a lightweight framework for delivering products in the face of uncertaintyI
Scrum is a team based methodology…Ideal team size is 5 to 9 peopleTeam has everything it needs to deliver an increment of working productVery clear role and responsibility delineation: ScrumMaster, Product Owner, TeamProduct Owner brings the whatTeam decides the howWIP is limited by the velocity of the teamScrumMaster’s job is to get rid of the stuff slowing the team down The idea is to deliver in short sprints…… use empirical process control, inspect and adaptTotally designed to be a lightweight framework for delivering products in the face of uncertaintyI
Explaining the hierarchy of value
Explaining the hierarchy of value
Explaining the hierarchy of value
So, before we get started, a little about me. My name is Mike Cottmeyer, I am an agile transformation coach with Pillar technology. Before I joined Pillar I was a trainer and consultant with VersionOne. Before that I ran a pretty large agile portfolio of projects for CheckFree (now Fiserv). Pillar Technology has been around for about 13 years and is just about 100 people strong. Pillar specializes in agile transformation and project delivery. We can bring in agile coaches on the leadership and project management side. We can bring in coaches to help you with TDD. We can spin up teams and help you deliver projects.