Skip to main content

Develop

Let’s do it!

  • Chapter
Agile Product Development
  • 2737 Accesses

Abstract

We all come up with lots of ideas every day despite varying levels of intelligence, experience, and exposure. Some people believe we might generate tens of thousands of ideas on a daily basis. While most ideas are fun to think about (imagine if we could move things by mere thoughts or if champagne flowed in municipal taps, just like water!), they are usually too impractical, obscure, wild, or outrageous to follow up on. Only a small percentage of ideas are actually worth pursuing.

This is a preview of subscription content, log in via an institution to check access.

Access this chapter

Chapter
USD 29.95
Price excludes VAT (USA)
  • Available as PDF
  • Read on any device
  • Instant download
  • Own it forever
eBook
USD 54.99
Price excludes VAT (USA)
  • Available as EPUB and PDF
  • Read on any device
  • Instant download
  • Own it forever
Softcover Book
USD 69.99
Price excludes VAT (USA)
  • Compact, lightweight edition
  • Dispatched in 3 to 5 business days
  • Free shipping worldwide - see info

Tax calculation will be finalised at checkout

Purchases are for personal use only

Institutional subscriptions

Notes

  1. 1.

    www.quotegarden.com/programming.html

  2. 2.

    “The 70,000 Thoughts Per Day Myth?” Neuroskeptic, http://blogs.discovermagazine.com/neuroskeptic/2012/05/09/the-70000-thoughts-per-day-myth/

  3. 3.

    “Managing the Development of Large Software Systems,” Dr. Winston Royce, www.serena.com/docs/agile/papers/Managing-The-Development-of-Large-Software-Systems.pdf

  4. 4.

    “Where Did the 40-Hour Workweek Come From?”

  5. 5.

    “XPXtudes,” http://c2.com/cgi/wiki?XpXtude

  6. 6.

    “Extreme Programming: A Gentle Introduction,” www.extremeprogramming.org/

  7. 7.

    “Interview with Kent Beck (circa 2001),” Jim Highsmith, https://dzone.com/articles/interview-kent-beck-circa-2001

  8. 8.

    “Declaration of Interdependence,” http://pmdoi.org/

  9. 9.

    “The New New New Product Development Game,” Hirotaka Takeuchi and Ikujiro Nonaka, https://hbr.org/1986/01/the-new-new-product-development-game

  10. 10.

    I haven’t come across anything in Sutherland’s or Schwaber’s literature that suggests they either collaborated with DeGrace and Stahl, or referred to their book. However, I am only referring to the publication dates to refer to the timeline, and by no means implicating that these two ideas are the same or different

  11. 11.

    “The History of Scrum,” www.scrumguides.org/history.html

  12. 12.

    “Hail Mary Pass,” https://en.wikipedia.org/wiki/Hail_Mary_pass

  13. 13.

    “The Scrum Guide,” www.scrumguides.org/scrum-guide.html

  14. 14.

    Ken Schwaber, co-creator of Scrum, wrote in his 2007 book The Enterprise and Scrum, “ There will be no Scrum Release 2.0 … Why not? Because the point of Scrum is not to solve [specific problems of development] … Scrum unearths the problems caused by the complexity and lets the organization solve them, one by one, over and over again”

  15. 15.

    https://media.ford.com/content/fordmedia/fna/us/en/news/2013/08/05/model-t-facts.html

  16. 16.

    “The Lean Mindset,” http://poppendieck.com/

  17. 17.

    “Evolutionary Project Management,” http://gilb.com/Project-Management

  18. 18.

    “The Kanban Method,” http://edu.leankanban.com/kanban-method

  19. 19.

    One could argue that if the user requirements are indeed complete, the product that would be built might only represent the time when those requirements were thought of; however, it is very likely that the world has moved on since then.

  20. 20.

    http://xp123.com/articles/invest-in-good-stories-and-smart-tasks/

  21. 21.

    “User Stories: An Agile Introduction,” www.agilemodeling.com/artifacts/userStory.htm

  22. 22.

    “User Stories,” www.mountaingoatsoftware.com/agile/user-stories

  23. 23.

    “Planning Poker in Details,” www.old-planningpoker.com/detail.html

  24. 24.

    “How Do Committees Invent?,” Melvin Conway, 1968, www.melconway.com/Home/Conways_Law.html

  25. 25.

    “Splitting User Stories: The Hamburger Method,” http://gojko.net/2012/01/23/splitting-user-stories-the-hamburger-method/

  26. 26.

    Epic Sharding, http://blog.pivotal.io/pivotal-labs/labs/epic-sharding

  27. 27.

    “Software Equation,” https://en.wikipedia.org/wiki/Software_equation

  28. 28.

    https://en.wikipedia.org/wiki/Three-point_estimation

  29. 29.

    “Critical Chain,” www.goldratt.co.uk/resources/critical_chain/

  30. 30.

    “How to Use Inch-Pebbles When You Think You Can’t,” www.jrothman.com/articles/1999/01/how-to-use-inch-pebbles-when-you-think-you-cant/

  31. 31.

    “The Cone of Uncertainty,” www.construx.com/Thought_Leadership/Books/The_Cone_of_Uncertainty/

  32. 32.

    “Student Syndrome,” https://en.wikipedia.org/wiki/Student_syndrome

  33. 33.

    “The Difference between a Story and a Task,” www.mountaingoatsoftware.com/blog/the-difference-between-a-story-and-a-task

  34. 34.

    “How to Decompose User Stories into Tasks,” www.payton-consulting.com/decompose-user-stories-tasks/

  35. 35.

    “User Story Mapping,” www.agileproductdesign.com/presentations/user_story_mapping/

  36. 36.

    “User Story Mapping,” http://jpattonassociates.com/user-story-mapping/

Author information

Authors and Affiliations

Authors

Rights and permissions

Reprints and permissions

Copyright information

© 2015 Tathagat Varma

About this chapter

Cite this chapter

Varma, T. (2015). Develop. In: Agile Product Development. Apress, Berkeley, CA. https://doi.org/10.1007/978-1-4842-1067-3_6

Download citation

Publish with us

Policies and ethics