The Color of Money - Priortization of User Tasks
7
drive UPA The Color of Money - An Agile Technique for Prioritization of Requirements Len Conte Feb 25, 2004
description
When migrating functionality from one platform to another (desktop to mobile) it can be difficult to understand which functionality should be the primary focus of initial release. We used the front-end of the CARD method (called the Big Picture) to gather tasks and affinitize them. We asked user surrogates to write down alll the tasks one per index card. We affinitized them in a collaborative session. We then went thru a validation and priotization exercise with a 10-12 customers (in the same room). We walked thru the tasks and had customers add/change/move the cards from the affinitization. We then prioritized tasks by importance and frequency. Finally we gave each customer 10 , $100 bills and had them pin their money to the tasks they felt we should migrate first. we then analyed the results in a grid using both priortization and dollars spent.
Transcript of The Color of Money - Priortization of User Tasks
drive
UPA
The Color of Money - An Agile Technique for Prioritization of Requirements
Len Conte
Feb 25, 2004
April 12, 20232
Big Picture – Target User
• Consumer Performance Engineer, DBA, IT Manager
• Performance Manager Manager Technical Infrastructure, Technical Services Manager
Performance Analyst Technical Analyst, System Administrator, System Architect, Level
2-3 Support
• Capacity Planner Capacity Planner, Capacity Analyst, System Analyst, Level 1
Support
April 12, 20233
Big Picture
50,000 foot view of the user’s work
• Define all the work involved with the user’s job
• Categorize all the tasks
• Rank all the tasks
› Frequency - H High, M Medium , L Low
› Importance - A High, B Medium, L Low
• Scope the system
April 12, 20234
“The Big Picture” Performance Analysts
Capacity Planning
Analysis
PerformanceBaselining
On DemandCapacity Planning
ContinuousCapacity Planning
Manage thePerformance Problem
KnowledgebaseOn Demand
Health CheckAnalyze
Performance I ssuesContinuous
Health Check
Process Management
Problem ProcessManagement
EPA ProcessManagement
Tool Administration& Operation
Tool MangementTool Eval, and Use
April 12, 20235
Where they spend their time
Tool Administration& Operation
Big Picture - Performance Analyst
1.0
Frequency of Task Importance of TaskH High
Medium
Low
High
Medium
LowL
Ma
A
C
B
Tool ManagementTool Eval, and Use
Collect performancedata
Get data that did nottransfer
Find out why datadidn't collect
Talk to BMC supportto solve product
problems
Run collectors indevelopment and QA
environments
Administrate DBspace for historical
database
Evaluate performanceproducts
Learn how to useperformance products
1 2
3
4
6
7
1.1 1.2
1 2 3 4Place sheets side by 5
Maintenance ofpresentation layer
8
Validate Productiondata collection
worked and data isvalid
Populate analyze
Apply patches
Load test.. validatedata consistency in
test environments ondemand
Set-up silent installf or 3rd partydistribution
I nstall sof tware
Troubleshoot install
Find out why collectagent did not run
Hardware tablemaintenance
Write scripts toensure reliability
9
10
11
12
13
14
15
16
17
18
H A
H A
H A
H A
Automate daily datacollection and
processing
5 H A
H A
H A
M B
H A
L C
H A
H A
1
2
3
L A L A
L A
L A
L B
L B
A
AM
M
April 12, 20236
Tasks analysis meeting
What our experts did:
› Add any missing “Analyst” activities Several key areas missing: Benchmark / Loadtesting
› Prioritize the tasks from their perspectives Frequency & Importance (Red/Yellow/Green)
› Decide what tasks BMC should focus onWe gave them $1,000 in fake $100 bills to spend (Top
10)!!
April 12, 20237
Where they spent the money
Note: Blue text denotes customer added task
Task $$ Frequency ImportanceGather other (non-BMC) metrics 700Identify performance problems / exceptions 700Correlate compare computer metrics with other data sources & correlation (SAS)500Workload characterization (global library) 500Analyze performance problems 400Proactively search for known performance issues 400Create summarized Performance view / End to end 400Observe and assist in benchmarking exercises 400Feed load test information into Predict 400 Not Assigned Not Assigned
Majority of customers (4 out of 7) 63% of $$4400Identify component of systems that are bottlenecks 300Compare actual usage with business measure usage/metrics 300Identify the category of performance problem 200Provide ad-hoc reports as required 200Disseminate performance data / graphs 200 Not Assigned
80/20 cut line 80% 5600Solve performance problems & make recommendations 100Report on performance problems & status 100Analyze Load test (Stress test) performance analysis 100Assets and configuration verification 100Identify trends & typical system behavior 100Identify SLA deviations 100Identify data profiles trends & typical system behavior 100Compare actual usage with forecast 100Establish performance (SLA) baselines 100Relate systems & applications metrics to business 100Determine threshold settings and correlate events for alerting 100Make threshold setting recommendations 100Define application process flow 100Predict the performance of an un-tested configuration 100
20% 1400
