-
Notifications
You must be signed in to change notification settings - Fork 0
/
3&4
55 lines (41 loc) · 2.97 KB
/
3&4
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
###### Chapter 3:The Project Management Process Groups
Project management consists of 10 knowledge areas
Integration, scope, schedule, cost, quality, resource, communications, risk, procurement, and stakeholder management
Projects involve five project management process groups
Initiating, planning, executing, monitoring and controlling, and closing
Holding a project kick-off meeting
It’s good practice to hold a kick-off meeting at the beginning of a project so that stakeholders can meet each other, review the goals of the project, and discuss future plans
Scrum Roles
Product owner: person responsible for the business value of the project and for deciding what work to do and in what order, as documented in the product backlog
ScrumMaster: person who ensures that the team is productive, facilitates the daily Scrum, enables close cooperation across all roles and functions, and removes barriers that prevent the team from being effective
Scrum team or development team: cross-functional team of five to nine people who organize themselves and the work to produce the desired results for each sprint, which normally lasts two to four weeks
Scrum artifact
Product backlog: list of features prioritized by business value
Sprint backlog: highest-priority items from the product backlog to be completed within a sprint
Burndown chart: shows the cumulative work remaining in a sprint on a day-by-day basis
Scrum ceremonies
Sprint planning session: meeting with the team to select a set of work from the product backlog to deliver during a sprint
Daily Scrum: short meeting for the development team to share progress and challenges and plan work for the day
Sprint reviews: meeting in which the team demonstrates to the product owner what it has completed during the sprint
Sprint retrospectives: meeting in which the team looks for ways to improve the product and the process based on a review of the actual performance of the development team
###### Chapter 4:Project Integration Management
Main processes
Develop the project charter
(Create an assumption log)
Develop the project management plan
(Direct and manage project execution)
(Manage project knowledge)
Monitor and control project work
Perform integrated change control
Close the project or phase
Common elements of a project management plan
Introduction/overview of the project
Description of how the project is organized
Management and technical processes used on the project
Work to be done
Schedule and budget information
References to other project planning documents
The project manager needs to focus on leading the project team and managing stakeholder relationships to execute the project management plan successfully
Project resource management, communications management, and stakeholder management are crucial to a project’s success
Project integration management ties together all the other areas of project management
Primary focus should be on project integration management