Chapter 7 Flashcards
Organizing a Project Team
Roles and Responsibilities Matrix
Is a tool used to identify all of the roles within a project and the associated responsibilities to the project work.
Responsibility Assignment Matrix (RAM)
Used to identify which tasks are assigned to which individuals.
RACI Chart
Similar to a RAM Chart but is uses the legend of:
Responsible
Accountable
Consult
Inform
Five types of project manager powers
Expert - The authority of the project manager comes from experience with the technology the project focuses on.
Reward/Penalty - The project manager has the authority to give or withhold something of value to the team members.
Formal (Positional Power) - The project manager has been assigned by senior management and is in charge of the project.
Coercive (Penalty Power) - The project manager has the authority to discipline the project team members.
Referent - The project teams personally know the project manager.
Subteam
Is simply a squadron of team members unique to one task within the project or within each geographical area.
Project Scheduler
The role is to help the project manager better create the schedule, identify risks and opportunities in the project, collect activity completion updates, and create a more cohesive environment in the project.
Six approaches to conflict resolution
Problem solving - Calls for additional research to find the best solution for the problem
Forcing - The person with the power makes the decision
Compromising - Requires both parties to give up something
Avoiding - the person who can make the decision simply avoids making a decision
Smoothing - The project manager minimizes the perceived size problem
Withdrawing - This is the worst conflict resolution approach, because one side of the argument walks away from the problem. The conflict is not resolved and it is considered a yield-lose solution
Scrum Master (Adaptive Projects)
This is analogous to the project manager, but the scrum master role is to coach, mentor, and ensure that everyone is following the rules of scrum. the scrum master isn’t directing people what to do through the project, but coaching people on what to do. The scrum master is sometimes called the “servant leader”.
Product Owner (Adaptive Projects)
The role is the business liaison between the team and the business people. This role is responsible for gathering, organizing and documenting the project requirements. Also responsible for prioritizing the requirements, called “user stories” in the product backlog.
Development Team (Adaptive Projects)
The development team describes the core workers of the agile project. The development team is self-led and self-organized.
Ceremonies (Adaptive Projects)
Are events or meetings in an adaptive project, specifically a scrum project. They are key events that are time boxed and represent the iterative nature of adaptive projects. Each role has specific responsibilities in each ceremony.
Sprint Planning (Adaptive Projects)
Sprint planning is the first ceremony of each sprint. During sprint planning the development team, product owner, and scrum master work together to select the most important items from the product backlog that the development team will create during the sprint.
Daily Scrum (Adaptive Projects)
Every workday in the sprint the development team and the scrum master meet for 15 minutes to answer three questions of each person:
What did you accomplish since our last meeting?
What will you work on today?
Are there any impediments or blockers preventing your progress?
Sprint Review (Adaptive Projects)
At the end of the sprint, the development team, product owner, scrum master, and key stakeholders meet for a demonstration by the development team. The sprint review is the development team demonstrating what they have accomplished during the last sprint.
Sprint Retrospective (Adaptive Projects)
This final ceremony of the sprint allows the development team, product owner, and scrum master to review what has and has not worked well in the project.
