Product Delivery

Celem prelekcji jest omówienie najważniejszych zagrożeń związanych z realizacją projektów i sposobów na przeciwdziałanie im. Bardzo często, mimo doskonałych umiejętności programistycznych oraz zarządczych, projekty nie są realizowane zgodnie z planem, czy oczekiwaniami klientów. Źródeł problemów należy szukać tak wewnątrz zespołu, jak i w komunikacji z klientem. Po wykładzie uczestnicy będą lepiej przygotowani do prowadzenia projektów, niezależnie od ich roli w zespole.

Transcript

1. Product delivery
2. Product delivery Agenda: What is product delivery? What product is? Customer expectations Customers perspective Developers perspective Backlog preparation Task vs feature vs use case Time estimation Prioritization Estimating task/feature business value What should be focused Presenting product/progress Done – Done Ownership Communication Common mistakes
3. Product delivery Product 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. What is product delivery?
4. Product delivery A product is anything that can be offered to a market that might satisfy a want or need What product is?
5. Product delivery 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. Customer expectations
6. Product delivery Customer specifies more or less what he wants to receive, and expects to have it in planned deadline and cost. Customers perspective
7. Product delivery Developer need a list of tasks to work on. Developers perspective
8. Product delivery What is backlog? It’s a list of requirements that is maintained for a product developed. It’s created to form a bridge between customers and developers perspective. Backlog preparation
9. Product delivery Use case – scenario how project can be use (consist of several features) Feature – functionality that can be used in product (consist usually of several tasks) Task – atomic thing to do by developer Use case vs feature vs task
10. Product delivery Process of finding estimate. After estimation we should be able to determine how much time each part of project will take. Time estimation
11. 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. Tasks despite being atomic, sometimes they are depending on different parts of system, which should be taken into consideration. Time estimation - tech debt
12. Product delivery 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 roadmap with milestones of project, and customer will know when he will receive each part to review. Prioritization
13. Product delivery Making core functionalities first has two main advantages: 1. More possibilities to test this part of application 2. More time to apply possible changes due to market needs changes Prioritization
14. Product delivery There is a big difference between approach of customer and developers. This difference should be handled using discussed means. Perspective summary Logged user can buy a watch # Logging in # Browsing watches # Making purchase Backlog
15. 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
16. Product delivery Project must be usable! What should be focused?
17. 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
18. Product delivery “All that’s left is to finish up the graphics, but other than that, it’s done.” Done - Done
19. Product delivery “Well, we’ll still need some final polishing, but it’s done.” Done - Done
20. Product delivery “I just need to run it thru some testing, but for now, it’s done.” Done - Done
21. Product delivery Do you think that sounds very done at all? It doesn’t. Done - Done
22. Product delivery Iterate, think about project usability and present your progress! Process summary Backlog Demo Demo
23. Product delivery Each member of a team should take responsibility for whole project. Ownership
24. Product delivery !!! Communication
25. Product delivery Bad estimates Being afraid to report problems Too narrow perspective - focusing the task without looking on the use case Common mistakes
26. Product delivery Summary Idea Backlog Product Delivered
27. Product delivery Questions & Answers
28. Product delivery Thank you for your attention!