Agile Project Management with Scrum (Microsoft Professional)

P

pay, employee, 113 ‚ 114

people, complexity of, 5

PERT chart management, 37, 38

Pigs, 7

plain language, using, 63 ‚ 65

planning

conversions to Scrum, 68

funders, working with, 67 ‚ 68

meetings. See Daily Scrum meetings; planning meetings, Sprint

minimum necessary, 68

Product Backlog component of, 68

questions resolved by, 67

stakeholder expectations, setting, 67

team ‚ s role in, 8, 134

visions , 68

planning meetings, daily. See Daily Scrum meetings

planning meetings, Sprint

attendees, 133

defined, 141

duration of, 8

first four hours, 133

parts , 8

Product Owner role at, 133, 134

redirection opportunities in, 17

rules of, 133 ‚ 134

second four hours, 134

Teams, role at, 134

time-boxing , 134

planning software example, 29 ‚ 31

precision, 2

predictability vs. estimates, 111

prioritization, benefits of, 148

process overview, 7 ‚ 9

Product Backlogs

bidding process, using during, 148

bugs , adding to, 131

burndown charts , 11 ‚ 12

Burndown reports , 89 ‚ 91

choosing items for Sprints, 133

columns in, 11

combined for multiple customers, 127

components of, 68

defined, 8, 141

example of, 10

example of constructing, 19 ‚ 21

explaining simply, 64

field service, 127

Gantt reports from, 87 ‚ 88

infrastructure for scaling, 120 ‚ 121

items, defined, 141

listing requirements for, 49

multiple customer scaling solution, 126 ‚ 129

multiple-team development of, 45, 56

planning, role in, 68

prioritizing in meetings, 8, 133

Product Owners goal for, 18

purpose of, 10

requirements management role, 153

ROI from, 18

rows in, 11

sale of company example, 61

scaling for multiple customers, 126 ‚ 129

scaling, prioritizing for, 120 ‚ 121

shadow creation of, 58 ‚ 60

spreadsheet parts, 11

Sprints, frozen during, 136

tracking function of, 85

uncertainty, reducing with, 41

Product Owners

customers, rivalries between, 58 ‚ 60

Daily Scrum involvement, 62

defined, 6, 141

financial impacts, importance of, 81

MegaBank example, 63 ‚ 65

MegaFund XFlow example, 57 ‚ 60

plain language, using, 63 ‚ 65

planning meetings, role in, 133, 134

prioritization of business problems, 20

Product Backlog construction example, 19 ‚ 21

Product Backlogs, explaining, 64

quick results, importance of, 55

responsibilities of, 74

ROI focus of, 18, 20

sale of company example, 61

scaling example, 128

ScrumMasters, relationship to, 36, 53, 65

Service 1st example, 55 ‚ 57

shadow creation of Product Backlogs, 58 ‚ 60

Sprint review meetings, 56 ‚ 57

Teams, relation to, 65, 112

Teams, tendency to drift from, 53

TechCore example, 60 ‚ 63

value of, 20 ‚ 21

project managers, 16, 25, 28, 30-31, 35-36, 104. See also ScrumMasters

project reports. See reports

public relations example, 31

purchasing components example, 62

purpose of Scrum, 1

Категории