AGILE TERMS 6 Word Scramble
|
Embed Code - If you would like this activity on your web page, copy the script below and paste it into your web page.
Normal Size Small Size show me how
Normal Size Small Size show me how
| Term | Definition |
| CHARACTERISTICS OF ADAPTIVE PLANNING | - ONGOING PROCESS - PROACTIVELY UPDATE W/ MULTIPLE MECHANISMS - FOCUS ON VALUE DELIVERY - UNCERTAINTY DRIVES REPLANNING - FREQUENTLY DISCOVER ISSUES - LOTS OF CHANGE |
| CHARACTERISTICS OF AGILE PLANS | - TRIAL & DEMO UNCOVER TRUE REQUIREMENTS LEADING TO REPLANNING - LESS UPFRONT, MORE THROUGHOUT PROJECT - MID-COURSE ADJUSTMENTS ARE THE NORM |
| FIRST 5 PRINCIPLES OF AGILE PLANNING | 1. PLAN AT MULTIPLE LEVELS 2. ENGAGE TEAM & CUSTOMER IN PLANNING 3. MANAGE EXPECTATIONS BY FREQUENTLY DEMONSTRATING PROGRESS 4. TAILOR PROCESS TO PROJECT 5. UPDATE PLAN BASED ON PRIORITIES |
| LAST 4 PRINCIPLES OF AGILE PLANNING | 6. ENSURE ESTIMATES ACCOUNT FOR RISK, DISTRACTIONS, & TEAM AVAILABILITY 7. USE APPROPRIATE ESTIMATION RANGES TO REFLECT UNCERTAINTY 8. BASE PROJECTIONS ON COMPLETION RATES 9. FACTOR IN DIVERSION & OUTSIDE WORK |
| ADDING MORE DETAILS AS INFORMATION EMERGES | PROGRESSIVE ELABORATION |
| ELEMENTS OF PROGRESSIVE ELABORATION | - PLANS - ESTIMATES - DESIGNS - TEST SCENARIOS |
| PLANNING AT MULTIPLE POINTS IN TIME AS DATA BECOMES AVAILABLE | ROLLING WAVE PLANNING |
| ASSESSING & PRIORITIZING BUSINESS VALUE OF WORK ITEMS & PLANNING ACCORDINGLY | VALUE-BASED ANALYSIS & DECOMPOSITION |
| BREAK DOWN REQUIREMENTS, PRIORITIZE THEM, & DESIGN PRODUCT BOX | VALUE-BASED DECOMPOSITION |
| KEEP REQUIREMENTS GENERAL THEN PROGRESSIVELY REFINE THEM | COARSE-GRAINED REQUIREMENTS |
| BENEFITS OF COARSE-GRAINED REQUIREMENTS | - BALANCES OVERALL DESIGN - DELAYS IMPLEMENTATION DECISION UNTIL LAST POSSIBLE MOMENT |
| SHORT, FIXED-DURATION TIME PERIODS WHERE WORK OR ACTIVITIES ARE UNDERTAKEN (IF WORK'S NOT DONE IN ONE, MOVE IT TO ANOTHER) | TIMEBOXING |
| DAILY STAND-UP TIMEBOX | 15 MINUTES |
| RETROSPECTIVES TIMEBOX | 2 HOURS |
| SPRINTS TIMEBOX | 1-4 WEEKS |
| WHY DO WE ESTIMATE? | TO DETERMINE WHICH PIECES OF WORK CAN BE DONE W/IN A RELEASE OR ITERATION |
| HOW ARE ESTIMATES CREATED? | BY PROGRESSING THROUGH THE STAGES OF PLANNING |
| HOW SHOULD ESTIMATES BE STATED? | IN RANGES |
| WHEN DO WE ESTIMATE? | DONE THROUGHOUT THE PROJECT & W/ MORE DETAIL LATER IN THE PROJECT |
| WHO PERFORMS ESTIMATES? | TEAM MEMBERS DO THEIR OWN ESTIMATES |
| TIME IT WOULD TAKE TO COMPLETE A GIVEN TASK ASSUMING ZERO INTERRUPTIONS OR UNPLANNED PROBLEMS | IDEAL TIME |
| LEVELS OF DECOMPOSING REQUIREMENTS | 1. EPICS 2. FEATURES 3. STORIES 4. TASKS |
Created by:
justin.olive1
Popular Management sets