Product delivery

What is product delivery?

What product is?

Done – Done

Tech debt

Customer expectations

Estimation

Prioritization

Presenting product/progress

Product delivery

Developers perspective

Customers perspective

Task vs feature vs use case

Ownership

Communication

Estimating task/feature business value

What should be focused

Common mistakes

Agenda:

Product delivery spans the entire lifecycle, from idea to customer

and market approval.

Product delivery

What is product delivery?

It involves everyone across the enterprise working together with

a shared understanding of how the product should solve customer

problems and satisfy needs.

Product delivery

A product is anything that can be offered to a market that might satisfy a want or need

What product is?

Product delivery

“All that’s left is to finish up the graphics, but other than that, it’s done.”

“Well, we’ll still need some final polishing, but it’s done.”

Done - Done

“I just need to run it thru some testing, but for now, it’s done.”

Do you think that sounds very done at all? It doesn’t.

Product delivery

Also known as “design debt” or “code debt”.

The debt can be thought of as work that needs to be done before

a particular job can be considered complete or proper. If the debt is

not repaid, then it will keep on accumulating interest, making it

hard to implement changes later on.

Tech debt

Customer expects to receive fully functional product.

He wants to be able to predict how big investment will be and when

we will be able to see the results.

Product delivery

Customer expectations

Product delivery

Process of finding estimate. After estimation we should be able to determine how much time each part of project will take.

Estimation

Product delivery

Process of determining, in cooperation with customer, which parts of project are most important and should be done first.

Prioritization

After estimation and prioritization, we should be able to present road-map with milestones of project, and customer will know when he will receive each part to review.

Product delivery

Each milestone (or even iteration if possible) should be finished with a demo, where customer can see results of work. Demonstration should be focused on newly added features, in a way that is as easy for the customer as possible.

Presenting product/progress

Product delivery

Developer need a list of tasks to work on.

Developers perspective

Product delivery

Customer specifies more or less what he wants to receive, and expects to have it in planned deadline and cost.

Customers perspective

Product delivery

Task – atomic thing to do by developer

Feature – functionality that can be used in product (consist usually

of several tasks)

Use case – scenario how project can be use (consist of several

features)

Task vs feature vs use case

Product delivery

Each member of a team takes responsibility for his part.

Ownership

Communication

Product delivery

!!!

Product delivery

When working on certain task, developer needs to keep in mind how it will be used and how it will affect use cases.

Estimating task/feature business value

Product delivery

Project must be usable!

What should be focused?

Product delivery

Too narrow perspective

Being afraid to report problems

Focusing the task without looking on the use case

Commom mistakes

Q & A

Product delivery

Product delivery

Thank you for your attention!