O slideshow foi denunciado.
Seu SlideShare está sendo baixado. ×

Product vs Project by Vivek Prahlad

Anúncio
Anúncio
Anúncio
Anúncio
Anúncio
Anúncio
Anúncio
Anúncio
Anúncio
Anúncio
Anúncio
Anúncio
Carregando em…3
×

Confira estes a seguir

1 de 80 Anúncio

Product vs Project by Vivek Prahlad

Baixar para ler offline

Vivek Prahlad shares his experiences on the differences and similarities between building software in the Product and Project contexts. At ThoughtWorks, he has spent approximately half of his career on the product side, and the other half on the consulting side. While the underlying principles are similar, there are often significant differences in terms of approaches that work for products and projects. Some of the differences we'll explore include: product vs. project inception, engineering considerations, testing approaches and strategies, course corrections, and more.

Vivek Prahlad shares his experiences on the differences and similarities between building software in the Product and Project contexts. At ThoughtWorks, he has spent approximately half of his career on the product side, and the other half on the consulting side. While the underlying principles are similar, there are often significant differences in terms of approaches that work for products and projects. Some of the differences we'll explore include: product vs. project inception, engineering considerations, testing approaches and strategies, course corrections, and more.

Anúncio
Anúncio

Mais Conteúdo rRelacionado

Diapositivos para si (20)

Quem viu também gostou (17)

Anúncio

Semelhante a Product vs Project by Vivek Prahlad (20)

Mais de Agile Software Community of India (20)

Anúncio

Mais recentes (20)

Product vs Project by Vivek Prahlad

  1. 1. Product vs Project Vivek Prahlad
  2. 2. My Background
  3. 3. ThoughtWorker for 8.5 years
  4. 4. Roughly half my time between Projects and Products
  5. 5. Tech lead
  6. 6. Agile Coach
  7. 7. Project manager
  8. 8. Product manager
  9. 9. Author of Frankenstein
  10. 10. Tech lead of Twist
  11. 11. So
  12. 12. Does agile work for Products?
  13. 13. Yes
  14. 14. Can you conceptualize, build and market Products from India?
  15. 15. Yes
  16. 16. Outsourcing should really be a four letter word.
  17. 17. U10g?
  18. 18. Before we begin
  19. 19. A few definitions
  20. 20. Project
  21. 21. Building software in (potentially) multiple releases
  22. 22. Support and evolution
  23. 23. Internal or External customers
  24. 24. Customers represented by Business Analysts, Domain experts
  25. 25. Goals?
  26. 26. Build something that solves a problem (or problems)
  27. 27. Secondary goals
  28. 28. Improve skills
  29. 29. Product?
  30. 30. Multiple releases
  31. 31. Functionality with each release
  32. 32. Invariably external users
  33. 33. Customers represented by Product Managers, Business Analysts
  34. 34. Goals?
  35. 35. Build something useful / valuable
  36. 36. Lines can be blurred
  37. 37. Would building a search engine be a product or project?
  38. 38. In my experience
  39. 39. Working on a product is a superset of project activities
  40. 40. Development activities roughly similar
  41. 41. Getting started
  42. 42. Business Plan
  43. 43. Inception
  44. 44. Business AND technical risk
  45. 45. Validating the business plan
  46. 46. Market research
  47. 47. Surveys
  48. 48. Analysts
  49. 49. Domain experts
  50. 50. Team composition
  51. 51. Development strategy
  52. 52. Addressing technical debt
  53. 53. Growing estimates?
  54. 54. Stability issues?
  55. 55. Testing strategy
  56. 56. Tests are a valuable asset
  57. 57. Problem:
  58. 58. Test execution time grows linearly
  59. 59. Solution?
  60. 60. Tools like Test load balancer can help split your test suite
  61. 61. Documentation?
  62. 62. Best handled as a part of a development
  63. 63. Documentation part of source control
  64. 64. Everything that changes part of source control
  65. 65. Demo scripts
  66. 66. Presentations
  67. 67. Usability testing results
  68. 68. Additional activities
  69. 69. Demos
  70. 70. Support
  71. 71. Feature requests and feedback
  72. 72. Usability testing
  73. 73. Planned capacity for these activities
  74. 74. Gotchas and Pitfalls
  75. 75. ‘Role bleed’
  76. 76. Getting the Architecture / Platform wrong
  77. 77. Not responding to feedback fast enough
  78. 78. Thank You!
  79. 79. Q &A

Notas do Editor

  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n

×