agile

xplanner

request for proposal
Requirements ---> don't call them
still do stories...and map to requirements

make matrix ...these are the requirements

helps with negotiation to find gaps

If you do this..then can do sm, med, large (need velocity)

in binder with relative sizes (make matrix could defend)
for example 570Points

Top ones were sprint with estimate (points)
Next sprint (points)
requirement -----> total points

Change requirement ----> estimate points (no changing sprint once in progress)

ts
nc
aos

new requirement (x pts) --- does customer want to pay for it, usually not so have to take out some other pts will then need to add to aos (this pts take into effect with change of in process pts)

Customer Price
if you ask fixed price then customer contract
* all risk on supplier

Supplier Contract
opposite time and material
* all risk on customer
- very low rates plus shared bonus on minimum knowing you are going to do more, we split the high price it was going to be. Must be agreement on bonus.


Need to make sure you include risk in price
enumerate the risks (my price is x because that is not need, complexity) Be explicit on why price is high

Given your high price but could give alternative staged price
for example, what is the three services you want us to work on (fixed price we prove scrum type of way we can deliver then you learn other stuff, so your priced will go down (in the rest risk lower because you know)).


need to know velocity of how many pts they team can do (know predictability)
if don't now get they team to start hacking together so you get a better prediction

Use 300% of points (if don't know your team)

* don't use agile and scrum words :)

want a system of tracability and tranperancy (does not use word of stories)

translate that ...

in the future we want to talk about these things this is the product owner

* look creative at process and lifecycle
we will give you X (the standard) AND
what ever language they use we use too for instance

freeze date X
but we are testing since day one.
1) we want business plan (product back log, estimates, and priorities)
trick is to have milestones fit in two week (iteration) and give more

"if you can't make the process fake it"
just fit your scrum to there process (give feedback and document one page or two sid that gives info they want)
need to be creative with simple metrics

Need Velocity
--------------------
1) M 65 p ----> should never be less than 65%
2) S 25 p
3) C 45 p
4) Y minimum 30 or 100 if really big and add to M
- want risk on business side so it can only get better

Total: 105 PTS

105 pts is what I want to deliver

what was my velocity 10 pts
that means I need 101/2 so 11

I would have to tell my product owner this is going to be 11 sprints
If product owner soes no say can only do 80 pts ...start negociating

Keep track of velocities


* not standard scrum

65 |
|
pts |________
time

| - make bugs timeline

shouldn't make distingquish between bug and feature, however bug guys want to know.

Bugs should be part of product (don't call it bug) except for legacy with integration
bugs bring things like fear and blame, don't promote this by calling it bug it is not added it is part of the size (it implies it - not time linked to it)

yes, we can do it but what do you want us not to do. you don't charge for every change if reasonable.

The product is initial target but when you finished it keep going

Burn up for product back log


Value
Risk
Cost
Operation
Learning


scrum alliance (tab of resources & tools)
scrum works (maybe a bit overwork)
xplanner
mingle (?)
teamfoundation
no microsoft project