Project delivery encompasses the entire lifecycle from idea conception to market approval, requiring collaboration across the enterprise to address customer needs effectively. It includes important aspects such as managing tech debt, setting customer expectations, and prioritizing project components for efficient delivery. Clear communication and demonstration of progress at each milestone are essential for maintaining alignment with customer goals.

1. Project delivery

2. What is project delivery?
What product is?
Done – Done
Tech debt
Customer expectations
Estimation
Prioritization
Presenting product/progress
Project delivery
Agenda:
Developers perspective
Customers perspective
Task vs feature vs use case
Ownership
Communication
Estimating task/feature business value
What should be focused
Common mistakes

3. Project delivery spans the entire lifecycle, from idea
to customer and market approval.
It involves everyone across the enterprise working together
with a shared understanding of how the product should solve
customer problems and satisfy needs.
Project delivery
What is project delivery?

4. A product is anything that can be offered to a market
that might satisfy a want or need.
Project delivery
What product is?

5. “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.”
“I just need to run it thru some testing, but for now, it’s done.”
Project delivery
Done - Done
It doesn’t.
Do you think that sounds very done at all?

6. 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.
Project delivery
Tech debt

7. 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.
Project delivery
Customer expectations

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

9. Process of determining, in cooperation with customer, which parts
of project are most important and should be done first.
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.
Project delivery
Prioritization

10. 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.
Project delivery
Presenting product/progress

11. Developer need a list of tasks to work on.
Project delivery
Developers perspective

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

13. TASK
FEATURE
USE CASE
Project delivery
Task vs feature vs use case
– atomic thing to do by developer
– functionality that can be used in product
(consist usually of several tasks)
– scenario how project can be use
(consist of several features)

14. Each member of a team takes responsibility for his part.
Project delivery
Ownership

15. Project delivery
Communication
!!!

16. When working on certain task, developer needs to keep
in mind how it will be used and how it will affect use cases.
Project delivery
Estimating task/feature business value

17. Project must be usable!
Project delivery
What should be focused?

18. Too narrow perspective
Being afraid to report problems
Focusing the task without looking on the use case
Project delivery
Common mistakes

19. Project delivery
Q & A

20. Thank you for
your attention!

21. mail@codete.com www.codete.com
It’s FREE!
SIGN UP FOR WEBINAR