Index_R

R

refactoring, 105

reports

Burndown reports, 89 ‚ 91

changes, 86 ‚ 87

customizing, pragmatic need for, 95

early Sprints, importance of, 94

extra frequency, 94

faking progress by ignoring debugging, 96

Gantt, 84 ‚ 91

lessons for, 99 ‚ 100

level of detail, meaningful, 99

MegaBank MBIT example, 92 ‚ 95

MegaEnergy example, 84 ‚ 92

paradigm shift from traditional, 86

Product Backlogs as, 85

purpose of, 83

reviews. See review meetings, Sprint

retrospective. See retrospective meetings, Sprint

sashimi rule for, 95

ScrumMaster role in, 86 ‚ 92

self-management , role in, 99

Service 1st example, 95 ‚ 99

specificity requirement, 98

technology progress, 93 ‚ 94

traditional approach, 84 ‚ 85

types for Scrum, 86

visibility requirement, 98

wolves demanding, 92 ‚ 95

Requests For Proposals (RFPs), 148 ‚ 149

requirements

listing for projects, 40

management, 152 ‚ 153

product. See Product Backlogs

reporting, 86

software, complexity of, 4 ‚ 5

traceability, 153

Requirements Management, 152 ‚ 153

retrospective meetings, Sprint

actionable items from, 139

attendance at, 138

defined, 141

example of, 108

purpose of, 102

rules for, 138 ‚ 139

time-boxing of, 138

return on investment. See ROI (return on investment)

review meetings, Sprint

artifacts, nonfunctional, 137

clean code requirement for, 105

defined, 9, 142

done, defined, 137

estimates vs. reality, assessing, 73

functionality rule, 137

hardware for presentations, 137

polling during, 138

preparing for, 137

purpose of, 137

rules for, 137 ‚ 138

scripted presentations in, 95

stakeholders role in, 138

time-boxing of, 137

RFPs (Requests For Proposals), 148 ‚ 149

ROI (return on investment)

adjustment intervals, 20

importance of, 81

Product Owners, focus of, 18, 20

roles

overview of, 6 ‚ 7

tasks assigned by, 39

rules of Scrum

changing, 133

Daily Scrum meetings, 135 ‚ 136

Sprint planning meetings, 133 ‚ 134

Sprint retrospective meetings, 138 ‚ 139

Sprint review meetings, 137 ‚ 138

Sprints, 136 ‚ 137