Best Practices for Software Product Development

5,255 views

Published on

Best Practices for Software Product Development

  1. 1. Best Practices for Software Product DevelopmentProf. Dr. A. MädcheChair of Information Systems IV, Business School andInstitute for Enterprise Systems (InES), University of Mannheimhttp://eris.bwl.uni-mannheim.dehttp://ines.uni-mannheim.deWalldorf, November 6th 2012
  2. 2. Agenda Agenda1 Motivation2 State-of-the-Art in Science and Practice3 Best Practices4 Summary 2
  3. 3. Motivation  Global competition  Global users Globalization  Global development teams Software Industrialization Consumerization Vendors • Cost pressure • Growing customer expectations • Shorter development cycles • Importance of user experience • Specialization & Standardization 3
  4. 4. Agenda Agenda1 Motivation2 State-of-the-Art in Science and Practice3 Best Practices4 Summary 4
  5. 5. (Software) Product DevelopmentKnowledge and Concepts from Research and Practice Information Science Practice Systems Product Vision Global Innovation & Strategy Software Management NPD Lean Product Development Marketing Research … R&D Development Management Coordination Product Pricinples Software Design Roadmapping Launch Engineering Lines Tactics Scrum Thinking & Release … … Mgt. Model-Driven Development Human Computer Design SWOT … Focus Groups Interaction Prototyping Marketing Management … Product Science GOMS Launch Psychology Team Composition & Performance 5
  6. 6. Science: Success Factors for Product Development(Management Science Perspective) (Brown & Eisenhardt, 1995) 6
  7. 7. Science: Usability MethodsAnalysis Card Sorting Focus Groups Scenarios Task Analysis Ethnography … Contextual Analysis PersonasDesign Wireframe Paper Sketches Guidelines Prototyping … High-Fidelity PrototypingEvaluation Survey Cognitive Walkthrough Think Aloud … Eye Tracking Usability Testing GOMS Analysis (Nielson, 1993), (Sharp, 2007), (Cooper, 2007) 7
  8. 8. Practice: Product Development in theAutomotive Industry  Prototyping  Milestone-based  Interdisciplinary 8
  9. 9. Practice: Product Development at AppleBased on an interview with Steve Jobs in 2010the following fundamental product developmentprinciples at Apple can be extracted:• User Experience Centric Design• Long-Term Vision• Deep Leadership Engagement• Small Focused Teams• Razor-sharp focus on your niche (R&D Management Blog, 2011) 9
  10. 10. Practice: SVPG Product Development Process Model Used by: (SVPG Website, 2012) 10
  11. 11. Agenda Agenda1 Motivation2 State-of-the-Art in Science and Practice3 Best Practices4 Summary 11
  12. 12. Best PracticesSix key best practices for software product development can be distilledfrom science and practice: Product Continuous Clear Product Vision & Stakeholder Scope Leadership Integration Focused, Inter- Artifact- Incremental disciplinary centric & Milestone- Empowered Development Based Teams Approach 12
  13. 13. Best Practice 1: Vision & Leadership Product Vision & Leadership Clear Product Scope Continuous Stakeholder Integration Focused, Inter- Incremental & Artifact-centric Milestone- disciplinary Develo-pment Based Empowered Teams Approach• Leadership Engagement: …• Clear Strategy & Long-Term Execution Plan: Company Product Product Strategy Strategy Planning 13
  14. 14. Best Practice 2: Focused, Inter- Product Vision & Leadership Clear Product Scope Continuous Stakeholder Integrationdisciplinary and Empowered Teams Focused, Inter- Incremental & Artifact-centric Milestone- disciplinary Develo-pment Based Empowered Teams Approach Cross-functional: Business, Design, and Technical Skills Decision Power: Roles & responsibilities Coordination & Communication: Constant information exchange, transparent hand-over Trust: performing team with moderate tenure 14
  15. 15. Best Practice 3: Clear Product Scope Product Vision & Leadership Clear Product Scope Continuous Stakeholder Integration Focused, Inter- Incremental & Artifact-centric Milestone- Scoping trades-off viability, desirability, disciplinary Develo-pment Based Empowered Teams Approach and feasibility. It is complex, requires time and competencies. Clear product scope is necessary condition for product execution (in new product development and development of release of an existing product) Explicit articulating product principles or design principles helps to establish shared understanding and to stay focused. 15
  16. 16. Best Practice 4: Artifact-Centric Product Vision & Leadership Clear Product Scope Continuous Stakeholder IntegrationDevelopment Focused, Inter- Incremental & Artifact-centric Milestone-People’s interactions with products are multisensory: disciplinary Develo-pment Based Empowered Teams Approachallow for active touching, exploring and interacting. 16
  17. 17. Best Practice 5: Continuous Stakeholder Product Vision & Leadership Clear Product Scope Continuous Stakeholder IntegrationIntegration Focused, Inter- Incremental & Artifact-centric Milestone- disciplinary Develo-pment Based EmpoweredContinuous integration of the various stakeholders in Teams Approachproduct development should be ensured: Suppliers & Services Buyer Ecosystem End-Users 17
  18. 18. Best Practice 6: Incremental & Milestone- Product Vision & Leadership Clear Product Scope Continuous Stakeholder IntegrationBased Approach Focused, Inter- Incremental & Artifact-centric Milestone- disciplinary Develo-pment Based Empowered Teams Approach Solution space is huge: Allow for incremental exploration to find an optimal solution for a given problem. However, there have to be milestones with explicit decision points, e.g. production execution should not be started without a clear scope. 18
  19. 19. Agenda Agenda1 Motivation2 State-of-the-Art in Theory and Practice3 Best Practices4 Summary 19
  20. 20. Summary 1 • (Software) product development requires a broad spectrum of soft and hard skills. • A comprehensive knowledge base in science and 2 practice providing insights for successful software product development exists • Six best practices for software product development 3 have been identified and based on existing work in science and practice. 20
  21. 21. Thank you for your attention! Q&A Prof. Dr. Alexander Mädche +49 621 181 3606 maedche@es.uni-mannheim.de Chair of Information Systems IV, Business School and Institute for Enterprise Systems, University of Mannheim http://eris.bwl.uni-mannheim.de http://ines.uni-mannheim.de 21
  22. 22. ReferencesBrown, S.L. & Eisenhardt, K.M., 1995. Product Development: Past Research, PresentFindings, and Future Directions. The Academy of Management Review, 20(2), p.353-378.Nielsen, J., 1993. Usability Engineering, Academic Press.Sharp, H., 2007. Interaction design : beyond human-computer interaction, Wiley.Cooper, A., 2007. About face 3 : the essentials of interaction design, Wiley.R&D Management Blog, 2011,http://rdmanagement.blogspot.de/2011/05/steve-jobs-methodology-for-apple-r.htmlSPVG Websites, 2012, http://www.svproduct.com/. 22

×