The Bespoke Software Product Factory (2007)
•
2 likes•1,057 views
A business plan for how to create a service company for building prodcuts based on the ideas of sotware market 3.0, open source and agile methods.
Recommended
More Related Content
What's hot
What's hot (20)
Similar to The Bespoke Software Product Factory (2007)
Similar to The Bespoke Software Product Factory (2007) (20)
More from Peter Antman
More from Peter Antman (20)
Recently uploaded
Recently uploaded (20)
The Bespoke Software Product Factory (2007)
- 1. Bespoke Software Product Factory Peter Antman Niklas Hagen Björn Hällström
- 2. SubVersion Maven Eclipse JUnit eXtreme Programming SCRUM Product Owner Sprint Subscription Software Market 3.0
- 4. get bundled software free or roll your own
- 6. Adapt to wrapped box
- 8. Assemble freely available parts
- 9. Linux
- 12. Cost of transaction almost zero
- 15. The Long Tail
- 16. Karaoke economy
- 19. We can use open source
- 20. We can contribute to open source
- 23. Commodification
- 24. Modularization
- 25. Standardization
- 27. Tom O'Reilly ”Software is no longer the primary locus of value in the computer industry. The commoditization of software drives value to services enabled by that software.”
- 29. There is a market for diversity
- 30. 57% of what Amazon sales was not available before Amazon existed
- 31. Where does Mogul fit in?
- 32. SubVersion Maven Eclipse JUnit eXtreme Programming SCRUM Product Owner Sprint Subscription Software Market 3.0 Customer
- 36. Typical IT department spend 50%-80% of time on support and maintenance
- 38. Loosing customers and sales
- 39. Less profits
- 40. Smaller budget for development
- 41. …etc.
- 44. An agile “assembly line”
- 45. SubVersion Maven Eclipse JUnit eXtreme Programming SCRUM Product Owner Sprint Subscription Software Market 3.0 Customer Project Process
- 49. Technology evolves and changes
- 50. End users expect new functionality and improvements - constantly
- 53. These 1000 perfectly described functions
- 54. Delivery May 1st
- 56. The first that has to be let loose is quality...
- 57. The second is delivery date...
- 58. The customer can’t change his mind..
- 59. No one is happy! Time Functionality Cost Quality
- 61. A certain cost per sprint (sprint subsciption)
- 63. The Service Model: Sprint Subscriptions
- 64. Sprint is the core unit of work Each sprint produces a working system that realises the business value the customer has expressed in the features that where part of the sprint backlog
- 66. involvment in a community
- 67. best pracitises
- 71. Add value on top
- 72. No home grown systems
- 73. gentrification Machine OS Database Application Server Application Application Stack Commodity Bespoke
- 76. continually re-estimate work needed and needed work
- 78. continually realize business needs (values) as software implementations
- 80. measure delivered value through unit tests
- 82. Product Management – from features to implementable user stories and tasks
- 83. Product Development – from user stories and tasks to implemented and tested functionality
- 84. Product Maintenance – support and issue management, continuous maintenance of the software stack used by the products Product Road Map Product backlog Product Release Support issues Product Management Product Development Product Maintenance Processes Product artifacts
- 89. efficiency
- 90. traceability Product Jira : Product and Sprint backlog, as well as Issue Management Subversion/FishEye : Version Management/Control Forum : Communication Wiki : Documentation Luntbuild : Continuous integration Acceptance Testing Time logging Collaboration Portal Dashboard portlets
- 93. SubVersion Maven Eclipse JUnit eXtreme Programming SCRUM Product Owner Sprint Subscription Software Market 3.0 Customer Project Process Development Process
- 95. Reuse of open source modules
- 96. Knowledge transfer through code access
- 97. “Scratch your own itch”
- 100. Process build to adapt to changes
- 101. release focused
- 102. quality control
- 103. SubVersion Maven Eclipse JUnit eXtreme Programming SCRUM Product Owner Sprint Subscription Software Market 3.0 Customer Projekt Process Development Process Tools
- 105. Eclipse and NetBeans as development environments
- 106. TestNG and JUnit for Unit-tests
- 107. Cactus and Cargo for integrations tests
- 108. Luntbuild for continous integration
- 109. Selenium for GUI acceptance tests
- 110. JBoss/Tomcat and Apache as server environments
- 112. Don't overdo it ("ta inte höjd…"): do only what is really needed
- 113. Refactor mercilessly: strive for optimal design
- 114. Develop coding standards: communicate ideas through the code
- 115. Create a common vocabulary: communicate ideas about the code
- 116. Use test-driven programming: prove the code works
- 117. Use pair-driven design and problem solving: use collective knowledge
- 118. Collective ownership of code: spreads responsibilities
- 119. Integrate often: handle effects of new features
- 120. Use short iterations: take small controllable steps
- 121. Release often: have a tight feed-back loop
- 122. OpenSource Java Bespoke Software / Applications SubVersion Maven Eclipse JUnit eXtreme Programming SCRUM Product Owner Sprint Subscription Software Market 3.0 Customer Project Process Development Process Tools
Editor's Notes
- För att bäst förstå hur Mogul ska bygga sitt erbjudande måste vi titta på vilken verklighet våra kunder lever i och fråga oss: -Hur hjälper vi bäst våra kunder att lyckas med sina affärer?
- Individanpassade produkter och tjänster Vi kunder vill ha allt mer individanpassade produkter och tjänster. Och eftersom teknologin gör det möjligt att leverera och vi kunder är kungar i överflödssamhället, vinner det företag som bäst matchar sina varor och tjänster med våra individuella behov.
- Eftersom informationen vill vara fri och informationsinnehållet i varor och tjänster ökar hela tiden, blir allting allt lättare att kopiera. Livscykeln för en vara eller en tjänst blir därför allt kortare, vilket i sin tur tvingar företag att allt oftare lansera produkter och nya tjänster och nya features. Företag måste fokusera på att kontinuerligt göra det de är bäst på, nämligen att utveckla sina produkter och tjänster
- Då har de inte tid att ägna sig åt sådant som inte är deras kärnverksamhet. T ex att utveckla applikationer och webtjänster. Undersökningar visar att en typisk intern IT-avdelning lägger mellan 50% och 80% av sina resurser på support och underhåll av den existerande applikationportföljen. Det betyder att det oftast blir tvärstopp eller enorma förseningar när de ska leverera något nytt. Och då tappar de kunder och försäljning. Förlorar lönsamhet. Får mindre budget för nyutveckling. Tappar ännu fler kunder och försäljning...
- Partner Därför måste dessa företag skaffa sig partners som är specialiserade på att utveckla skräddarsydda applikationer Applikationer som tål snabb affärsutveckling utan att de blir underhållsbördor. En partner som kontinuerligt hjälper dem att utveckla nya features i befintliga applikationer eller nya applikationer.
- Vi erbjuder våra kunder att: Abonnera på sprintar = ny funktionalitet som realiserar affärsvärden Betala för det du använder Utvecklingstjänsten/produktionstjänsten Support Vi skapar team som är små mjukvaruföretag Med egna produktionslinor
- Renovation of software through (continuous) refactoring of older,”home made” and non-standardised parts by replacing them with standardised components and architectures. Mogul’s gentrification approach aims at building applications as far as possible based on standard products (mainly Open Source based products) and to move the commoditisation as far up in the application as possible. The goal is that only the unique parts of an application will need to be maintained and developed.