Il product development - 20 01 2011

920 views

Published on

Published in: Technology, Business
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
920
On SlideShare
0
From Embeds
0
Number of Embeds
643
Actions
Shares
0
Downloads
1
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Il product development - 20 01 2011

  1. 1. Product Development Approach Moscow, 2011
  2. 2. <ul><li>World-class innovation products and solutions development in Russia; </li></ul><ul><li>Innovation as the main competitive advantage for the global market entry with IT products and Web 2.0 projects (USA, Russia, Europe, Asia); </li></ul><ul><li>Innovation as the only possible breakthrough element in Knowledge Economy for Russian Federation; </li></ul><ul><li>Innovation as the major model for sustainable business development; </li></ul><ul><li>Global innovation as attractive environment for the best Russian professionals. </li></ul>Mission
  3. 3. <ul><li>INDePT introduction; </li></ul><ul><li>Case study project SOPRAX; </li></ul><ul><li>Tools and techniques. </li></ul>Table of content
  4. 4. INDePT | Process Methodology Overview <ul><li>INDePT methodology is designed to provide flexibility, visibility and productivity to the whole life cycle of product development. </li></ul><ul><li>INDePT methodology is agile, incremental and highly iterative. </li></ul><ul><li>Six major attributes in the process: </li></ul><ul><li>Customer Problems, </li></ul><ul><li>Questions, </li></ul><ul><li>Functionality, </li></ul><ul><li>Feature Sets, </li></ul><ul><li>Features </li></ul><ul><li>Metrics. </li></ul>
  5. 5. INDePT | Process Iterations <ul><li>There are five major iterations in a process: </li></ul><ul><li>Customer Problem Domain Analysis; </li></ul><ul><li>System Functionality and Objects Analysis; </li></ul><ul><li>System Design; </li></ul><ul><li>Prototyping and Object Architecture; </li></ul><ul><li>Features Partition and Coding and Rollout iterations. </li></ul>
  6. 6. INDePT | Phases <ul><li>Overall, methodology consists of three generic phases: </li></ul><ul><li>Analysis </li></ul><ul><li>Design and Development </li></ul><ul><li>Rollout. </li></ul><ul><li>Each phase represents a number of iterations with numerous inspections. </li></ul><ul><li>The main principle of the process is timely communication, visible progress and monitored productivity and efficiency. </li></ul>
  7. 7. INDePT | Analysis phase <ul><li>Iteration 1 - Customer Problem Domain Analysis: </li></ul><ul><li>An initial project-wide iteration conducted by problem domain experts/analysts at customer site (preferable). </li></ul><ul><li>A high-level walkthrough of the scope of the system and its context is performed. </li></ul><ul><li>Detailed domain walkthroughs are then held for each area to be modeled and developed. </li></ul><ul><li>Normally takes 2 iterations (for small-scale projects 1 iteration should be sufficient). </li></ul><ul><li>Iteration 2 - System Functionality and Objects Analysis: </li></ul><ul><li>Continuation of the initial process focus is placed on functionality of the system. </li></ul><ul><li>Normally takes 2-3 iterations for middle-large scale projects </li></ul>
  8. 8. INDePT | Design and Development phase <ul><li>Iteration 1 - System Design, Prototyping and Objects Architecture Iteration: </li></ul><ul><li>Refines the functionality of the system to the feature set level of granularity and initial description of the features. </li></ul><ul><li>Functional prototype presents the major functionality. </li></ul><ul><li>System design and architecture is formed with detailed definition of objects definition and dependencies. </li></ul><ul><li>Normally 3-5 iterations for middle-large scale projects </li></ul><ul><li>Iteration 2 - Features Partition and Coding Iteration: </li></ul><ul><li>Activity with domain and development members under the guidance of Project Manager and Chief Architect. </li></ul><ul><li>A low-level module partitioning (feature level) is performed and appropriate feature sets/features are added into the Project Plan with commitment dates. </li></ul><ul><li>Normally 2-3 iterations for middle-large scale projects. </li></ul>
  9. 9. INDePT | Metrics <ul><li>Process metrics provides factual information on current team productivity and performance patterns and enable managers to asses the current progress with maximum visibility and realistic information. </li></ul><ul><li>Quantitative metrics: </li></ul><ul><li>Actual/Planned Completion Date for the Feature; </li></ul><ul><li>Actual/Planned Completion Date for the Feature Set; </li></ul><ul><li>Number of days spent on Analysis Iterations </li></ul><ul><li>Number of Defects found in Feature Set </li></ul><ul><li>Number of Open/Closed Defects </li></ul><ul><li>Number of Assigned (Open) Defects per Developer </li></ul><ul><li>Qualitative metrics: </li></ul><ul><li>Number of Severity (1, 2) Defects per Developer </li></ul><ul><li>Complexity Ranking of the Modules </li></ul><ul><li>Urgency Ranking of the Modules </li></ul>
  10. 10. INDePT | Rollout Iteration <ul><li>Rollout iteration provides integration and configuration of the whole system online or on customer site. </li></ul><ul><li>Activity with domain and development members under the guidance of Project Managers from both sides. </li></ul><ul><li>Developed modules are configured and released online. </li></ul><ul><li>Major module inspections/documentation/testing procedures are reviewed and verified </li></ul>
  11. 11. INDePT | Methodology scheme
  12. 12. SOPRAX | The idea (Social Promo Accelerator) Social net + e-Shop
  13. 13. SOPRAX | Analysis phase result Feature set Features Features Features Features Feature set Feature set Feature set Feature set
  14. 14. SOPRAX | Technical specification <ul><li>Roles </li></ul><ul><li>Detailed site map </li></ul><ul><li>Technical requirements </li></ul>
  15. 15. SOPRAX | Designs <ul><li>System architecture design </li></ul><ul><li>Deployment diagram </li></ul>
  16. 16. SOPRAX | Design prototyping: e-Shop <ul><li>e-Shop page sketch </li></ul><ul><li>e-Shop page HTML layout </li></ul>
  17. 17. SOPRAX | Design prototyping: user profile <ul><li>User profile page sketch </li></ul><ul><li>User profile page HTML layout </li></ul>
  18. 18. SOPRAX | The final portal <ul><li>e-Shop part </li></ul><ul><li>Social part </li></ul>
  19. 19. SOPRAX | Project planning
  20. 20. SOPRAX | Process metrics
  21. 21. Tools | Used tools and techniques <ul><li>Destination </li></ul>Java <ul><li>Scheduler </li></ul>Teamcity <ul><li>XML Build tools </li></ul>Maven <ul><li>Test tools </li></ul><ul><li>JUnit (unit tests) </li></ul><ul><li>Cobertura (test coverage) </li></ul><ul><li>Jalopy (code style) </li></ul><ul><li>PMD (code analysis) </li></ul><ul><li>EMMA (code coverage) </li></ul><ul><li>Selenium (UI tesing) </li></ul><ul><li>JMeter (performance testing) </li></ul><ul><li>IDE </li></ul>Netbeans, Eclipse, Intelleij Idea <ul><li>Version control </li></ul>Subversion <ul><li>Documentation </li></ul>Confluence, JavaDoc, Adobe Acrobat <ul><li>Project Planning </li></ul>MS Project
  22. 22. Tools | Document repository <ul><li>Project directory </li></ul><ul><li>An article example </li></ul>
  23. 23. Tools | SVN – Code version control
  24. 24. Tools | Continuous integration
  25. 25. Tools | Bug tracking system
  26. 26. Tools | Automated testing
  27. 27. Created by Innovation Lab LLC

×