The document discusses key aspects of project management using an Agile approach. It defines what projects are and aren't, and describes different common project approaches like Waterfall and Agile. It outlines the Scrum process used in Agile, including sprints, product and sprint backlogs, and roles like the Scrum Master and Product Owner. It emphasizes values like commitment, openness, focus and courage needed to implement Agile successfully in a business.
19. The scrum master is the project leader and person who works with IT professionals each day. They keep the project on track, on budget, and with high quality. They should be good with people and have a solid grounding in technology. The Product Owner works with the Scrum Master. They understand the business and customers who use the product. They should be experienced pros who can take vague requirements and turn them into a concrete to do list.
20. The pigs on the project are the ones who make it a reality. They are the ones who are committed and have the most to loose if the project fails. These are your IT professionals. The Chickens are the ones involved with the project. They don’t have as much invested and their career is not as impacted by project failure. These people can affect the project in both positive and negative ways. These are sales people, marketing professionals, accounting types, and the legal department
21.
22.
23.
24.
25.
26.
27.
28.
29.
30.
31.
32.
Notas del editor
People talk about projects all the time but before we begin we really need a few definitions of what projects are and are not.
Have you had a conversation like this.
Who fill the roles of Chickens and Pigs in your office. Can you understand their different approaches to projects. IT people are usually your pigs.
Discuss the project pyramid, scope, schedule, Resources.
The is how we deal with structural ambiguity.
Now you know why it is called waterfall. The further down you go the more expensive changes become.
Remember a sprint is not a hamster wheel. Their must be downtimes between sprints and their must be meetings to follow up on lessons learned after each sprint.
Remember in Managing geeks this is how you deal with task ambiguity.
These are not stereotypes but roles which govern how the project is completed.
Remember the product backlog is created by the users, the sprint backlog is agreed upon by the product owner, scrum master and team, the sprints are performed by your chickens and pigs, the product is for your customers. Managers set priorities technologists set timelines and each must be respected by the other side.
Each scrum should have each person ask the following questions: What did you do yesterday? What are you going to work on today? Are their any risks preventing you from getting your job done today?