Here I annotate some keywords from topics related to customers and how software provide value to them.
For further investigations, learning.
Maybe a Product Owner course could help here.
Scrum prescribe that
- Product backlog items should be prioritized and the priority is driven by risk, value, and necessity.
- Product backlog items have also an estimate of the effort required to turn the each into a potentially shippable functionality
- Product Owner is the one and only person responsible for ensuring the value of the work the Team performs
- Product Owner for commercial development may be the product manager. For in-house development could be the manager of the business function that is being automated.
Note also that the effort, in whatever unit of work have been decided, is proportional to the time required to implement the item. The item is implemented when it meet the definition of "done" of the team.
Notes collected from various reading
- A well-prioritized product backlog drive profitable growth
It depend on
- the business exchange model (similar to the value stream in Lean I would say): how you trade money for value in software
- the profit engine: how you structure your relationship with your market to drive increasing exchanges of value
- Some financial metrics of revenue vs. costs:
- Incremental Funding Methodology (IFM) and Minimum Marketable Features (MMF): http://en.wikipedia.org/wiki/Incremental_funding_methodology
- Every P.O. and customer have different propensity to risks, different constraint and feel different pressure about timing of events, different beliefs about the probability that and event will actually happen.
- A P.O. and a customer may be more focused on time (the release date) or more focused on features (the feature that must be finished first)
- Seed funding, http://en.wikipedia.org/wiki/Seed_funding
Print | posted @ domenica 4 luglio 2010 22:26