Your SlideShare is downloading. ×
0
Harry Lin  林書華 Trend Micro Inc.  趨勢科技 March 18, 2003 Software Product Development Life Cycle
Agenda <ul><li>Product development life cycle overview </li></ul><ul><li>Requirement phase </li></ul><ul><li>Project plann...
Product Development Life Cycle <ul><li>Software development project characteristics </li></ul><ul><li>Requires domain know...
Product Development Life Cycle <ul><li>Software Development Process </li></ul><ul><li>Is the path along which project evol...
Product Development Life Cycle <ul><li>Software Project Requirements </li></ul><ul><li>An agreed upon and identical projec...
Product Development Life Cycle <ul><li>The Product Development Life Cycle is a template that a software development group ...
Product Development Life Cycle <ul><li>It also explains the standard Product Development process that development teams sh...
Product Development Life Cycle <ul><li>The Product Development process helps efficiently employ and allocate resources. Wh...
Benefits of an Effective Process <ul><li>Changes are controlled systematically: the change is requested, the impact analyz...
Benefits of an Effective Process <ul><li>Predictable: Managers and project sponsors need projects to be predictable, to pr...
Phases of Product Development  <ul><li>Requirements phase: This is a product planning and business evaluation stage. The p...
Phases of Product Development  <ul><li>Detailed Design phase: During this phase all departments of the product development...
Phases of Product Development  <ul><li>Pre-Release phase (Alpha and Beta): While developing a product in the Pre-Release p...
Phases of Product Development  <ul><li>Closure phase: After the product is released the project still must pass this cruci...
Requirement Phase <ul><li>The first stage in developing a product is identifying what to build during the entire Product D...
Requirement Phase <ul><li>This is also the period during which the Marketing, the PM, and the implementation team work clo...
Requirement Phase <ul><li>The MRD should include the following:  </li></ul><ul><ul><li>Mission statement  </li></ul></ul><...
Requirement Phase <ul><li>A PRD should also have an Engineering resource commitment and an estimated schedule. A more accu...
Requirement Phase <ul><li>The review for these documents (MRD/PRD) is very important to enhance the quality of these docum...
Project Planning/High Level Design Phase <ul><li>Project planning is essential to the project's success. It provides the b...
Project Planning/High Level Design Phase <ul><li>Major milestones in the project plan include:  </li></ul><ul><ul><li>MRD ...
Project Planning/High Level Design Phase <ul><li>The purpose of the Planning phase is to plan the project and formulate th...
Project Planning/High Level Design  Phase <ul><li>This product development phase involves mapping the goals and objectives...
Project Planning/High Level Design  Phase <ul><li>Although no code is generated during this phase, it may seem that the ac...
Detail Design Phase <ul><li>The purpose of the Detailed Design phase is to finalize the design and complete the test plan ...
Construction Phase <ul><li>The purpose of the Construction phase is to implement the design stage by stage. At this point,...
Construction Phase <ul><li>The Construction phase can be divided into recurring stages. A wrap-up meeting should conclude ...
Pre-release Phase <ul><li>While entering the Pre-Release phase, the focus on the Implementation team should switch from co...
Pre-release Phase <ul><li>In some projects, the period between feature complete and the first alpha build is called pre-al...
Alpha <ul><li>Before Alpha cycle, major functions of the product should be complete while minor functions may still be und...
Alpha <ul><li>The focus of the team during the Alpha is to get the product out the door and to eliminate the possibility o...
Activities During Alpha <ul><li>Tune Performance  </li></ul><ul><li>Conduct QA Alpha Test  </li></ul><ul><ul><li>Regressio...
Activities During Alpha <ul><li>Conduct Super Lab Test  </li></ul><ul><li>Conduct Internal Test Using IT Production Server...
Beta <ul><li>During the Beta cycle, all product features are implemented and code development is stopped. Code freezing be...
Beta <ul><li>The Beta plan serves as a guiding policy on objectives of Beta and Beta criteria, to guide the Beta customer ...
Closure <ul><li>The purpose of the Closure phase is to release the product and to conclude the experience and lessons from...
Closure <ul><li>Major Activities </li></ul><ul><ul><li>Endorsement Meeting  </li></ul></ul><ul><ul><li>Post-Mortem Meeting...
Project Management – Planning <ul><li>A good planning is a good start of the project </li></ul><ul><li>Include all functio...
Project Management – Planning <ul><li>Identifies and resolves project risks </li></ul><ul><li>Schedule actions for risks a...
Project Management – Risk Management <ul><li>Any exceptions that prevent the project team from reaching the project goal a...
Project Management – Monitoring <ul><li>Docs in planning phase are the baseline for the project </li></ul><ul><li>Use base...
Project Management – Monitoring <ul><li>Provides other departments with regular project status reports </li></ul><ul><li>M...
Project Management – Status Reporting <ul><li>Not only outside world needs to know the project status, so does every proje...
Project Management – Change Control <ul><li>Every change go through Change Control Process </li></ul><ul><li>Once committe...
Upcoming SlideShare
Loading in...5
×

Product Development ..

998

Published on

0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
998
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
18
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide
  • Please provide a revenue chart breakdown by regions (US, Asia, and Europe), by platforms, and by quarters. So we can better understand the revenue trend and put our resources on the critical factors
  • Please provide a revenue chart breakdown by regions (US, Asia, and Europe), by platforms, and by quarters. So we can better understand the revenue trend and put our resources on the critical factors
  • Please provide a revenue chart breakdown by regions (US, Asia, and Europe), by platforms, and by quarters. So we can better understand the revenue trend and put our resources on the critical factors
  • Please provide a revenue chart breakdown by regions (US, Asia, and Europe), by platforms, and by quarters. So we can better understand the revenue trend and put our resources on the critical factors
  • Please provide a revenue chart breakdown by regions (US, Asia, and Europe), by platforms, and by quarters. So we can better understand the revenue trend and put our resources on the critical factors
  • Please provide a revenue chart breakdown by regions (US, Asia, and Europe), by platforms, and by quarters. So we can better understand the revenue trend and put our resources on the critical factors
  • Please provide a revenue chart breakdown by regions (US, Asia, and Europe), by platforms, and by quarters. So we can better understand the revenue trend and put our resources on the critical factors
  • Please provide a revenue chart breakdown by regions (US, Asia, and Europe), by platforms, and by quarters. So we can better understand the revenue trend and put our resources on the critical factors
  • Please provide a revenue chart breakdown by regions (US, Asia, and Europe), by platforms, and by quarters. So we can better understand the revenue trend and put our resources on the critical factors
  • Please provide a revenue chart breakdown by regions (US, Asia, and Europe), by platforms, and by quarters. So we can better understand the revenue trend and put our resources on the critical factors
  • Please provide a revenue chart breakdown by regions (US, Asia, and Europe), by platforms, and by quarters. So we can better understand the revenue trend and put our resources on the critical factors
  • Please provide a revenue chart breakdown by regions (US, Asia, and Europe), by platforms, and by quarters. So we can better understand the revenue trend and put our resources on the critical factors
  • Please provide a revenue chart breakdown by regions (US, Asia, and Europe), by platforms, and by quarters. So we can better understand the revenue trend and put our resources on the critical factors
  • Please provide a revenue chart breakdown by regions (US, Asia, and Europe), by platforms, and by quarters. So we can better understand the revenue trend and put our resources on the critical factors
  • Please provide a revenue chart breakdown by regions (US, Asia, and Europe), by platforms, and by quarters. So we can better understand the revenue trend and put our resources on the critical factors
  • Please provide a revenue chart breakdown by regions (US, Asia, and Europe), by platforms, and by quarters. So we can better understand the revenue trend and put our resources on the critical factors
  • Please provide a revenue chart breakdown by regions (US, Asia, and Europe), by platforms, and by quarters. So we can better understand the revenue trend and put our resources on the critical factors
  • Please provide a revenue chart breakdown by regions (US, Asia, and Europe), by platforms, and by quarters. So we can better understand the revenue trend and put our resources on the critical factors
  • Please provide a revenue chart breakdown by regions (US, Asia, and Europe), by platforms, and by quarters. So we can better understand the revenue trend and put our resources on the critical factors
  • Please provide a revenue chart breakdown by regions (US, Asia, and Europe), by platforms, and by quarters. So we can better understand the revenue trend and put our resources on the critical factors
  • Please provide a revenue chart breakdown by regions (US, Asia, and Europe), by platforms, and by quarters. So we can better understand the revenue trend and put our resources on the critical factors
  • Please provide a revenue chart breakdown by regions (US, Asia, and Europe), by platforms, and by quarters. So we can better understand the revenue trend and put our resources on the critical factors
  • Please provide a revenue chart breakdown by regions (US, Asia, and Europe), by platforms, and by quarters. So we can better understand the revenue trend and put our resources on the critical factors
  • Please provide a revenue chart breakdown by regions (US, Asia, and Europe), by platforms, and by quarters. So we can better understand the revenue trend and put our resources on the critical factors
  • Please provide a revenue chart breakdown by regions (US, Asia, and Europe), by platforms, and by quarters. So we can better understand the revenue trend and put our resources on the critical factors
  • Please provide a revenue chart breakdown by regions (US, Asia, and Europe), by platforms, and by quarters. So we can better understand the revenue trend and put our resources on the critical factors
  • Please provide a revenue chart breakdown by regions (US, Asia, and Europe), by platforms, and by quarters. So we can better understand the revenue trend and put our resources on the critical factors
  • Please provide a revenue chart breakdown by regions (US, Asia, and Europe), by platforms, and by quarters. So we can better understand the revenue trend and put our resources on the critical factors
  • Please provide a revenue chart breakdown by regions (US, Asia, and Europe), by platforms, and by quarters. So we can better understand the revenue trend and put our resources on the critical factors
  • Please provide a revenue chart breakdown by regions (US, Asia, and Europe), by platforms, and by quarters. So we can better understand the revenue trend and put our resources on the critical factors
  • Please provide a revenue chart breakdown by regions (US, Asia, and Europe), by platforms, and by quarters. So we can better understand the revenue trend and put our resources on the critical factors
  • Please provide a revenue chart breakdown by regions (US, Asia, and Europe), by platforms, and by quarters. So we can better understand the revenue trend and put our resources on the critical factors
  • Please provide a revenue chart breakdown by regions (US, Asia, and Europe), by platforms, and by quarters. So we can better understand the revenue trend and put our resources on the critical factors
  • Please provide a revenue chart breakdown by regions (US, Asia, and Europe), by platforms, and by quarters. So we can better understand the revenue trend and put our resources on the critical factors
  • Please provide a revenue chart breakdown by regions (US, Asia, and Europe), by platforms, and by quarters. So we can better understand the revenue trend and put our resources on the critical factors
  • Please provide a revenue chart breakdown by regions (US, Asia, and Europe), by platforms, and by quarters. So we can better understand the revenue trend and put our resources on the critical factors
  • Please provide a revenue chart breakdown by regions (US, Asia, and Europe), by platforms, and by quarters. So we can better understand the revenue trend and put our resources on the critical factors
  • Please provide a revenue chart breakdown by regions (US, Asia, and Europe), by platforms, and by quarters. So we can better understand the revenue trend and put our resources on the critical factors
  • Please provide a revenue chart breakdown by regions (US, Asia, and Europe), by platforms, and by quarters. So we can better understand the revenue trend and put our resources on the critical factors
  • Please provide a revenue chart breakdown by regions (US, Asia, and Europe), by platforms, and by quarters. So we can better understand the revenue trend and put our resources on the critical factors
  • Please provide a revenue chart breakdown by regions (US, Asia, and Europe), by platforms, and by quarters. So we can better understand the revenue trend and put our resources on the critical factors
  • Please provide a revenue chart breakdown by regions (US, Asia, and Europe), by platforms, and by quarters. So we can better understand the revenue trend and put our resources on the critical factors
  • Please provide a revenue chart breakdown by regions (US, Asia, and Europe), by platforms, and by quarters. So we can better understand the revenue trend and put our resources on the critical factors
  • Transcript of "Product Development .."

    1. 1. Harry Lin  林書華 Trend Micro Inc.  趨勢科技 March 18, 2003 Software Product Development Life Cycle
    2. 2. Agenda <ul><li>Product development life cycle overview </li></ul><ul><li>Requirement phase </li></ul><ul><li>Project planning/High level design phase </li></ul><ul><li>Detail design phase </li></ul><ul><li>Constructions phase </li></ul><ul><li>Pre-release phase </li></ul><ul><li>Closure </li></ul><ul><li>Project management </li></ul><ul><ul><li>Planning </li></ul></ul><ul><ul><li>Risk management </li></ul></ul><ul><ul><li>Project monitoring </li></ul></ul><ul><ul><li>Change Control </li></ul></ul>
    3. 3. Product Development Life Cycle <ul><li>Software development project characteristics </li></ul><ul><li>Requires domain knowledge and technology </li></ul><ul><li>Is a disciplined activities of creativity </li></ul><ul><li>Is a team work with huge amount of communication </li></ul><ul><li>Needs a lot of tools and various expertise </li></ul><ul><li>Evolves in a changing environment </li></ul>
    4. 4. Product Development Life Cycle <ul><li>Software Development Process </li></ul><ul><li>Is the path along which project evolves, deliverables mark the progress </li></ul><ul><li>The bigger scope the project is, the more powerful the process is </li></ul><ul><li>Essentials behind the process is more important than the process itself </li></ul><ul><li>Quality of the product is as good as the quality of the process </li></ul>
    5. 5. Product Development Life Cycle <ul><li>Software Project Requirements </li></ul><ul><li>An agreed upon and identical project vision, mission, objective shared among team members </li></ul><ul><li>Has specific start and end dates, defined objectives, established responsibilities, budget and schedule </li></ul><ul><li>A jelled team with required expertise </li></ul><ul><li>A leader who drives the project toward the objective everyday </li></ul><ul><li>A clearly defined collaborative model inside the team and to the outside world </li></ul><ul><li>Visible, accountable, traceable, and controllable </li></ul>
    6. 6. Product Development Life Cycle <ul><li>The Product Development Life Cycle is a template that a software development group can use for project customization. </li></ul><ul><li>  </li></ul><ul><li>It illustrates each development phase in detail: from gathering information to defining what product to create to developing the product, from releasing the product to the market to training technical support engineers. </li></ul><ul><li>  </li></ul>
    7. 7. Product Development Life Cycle <ul><li>It also explains the standard Product Development process that development teams should follow. The key positions and the lead personnel in the different stages of the development process are also identified. </li></ul><ul><li>The Product Development process integrates people and tools from different departments to develop software. These include: </li></ul><ul><ul><li>Product Managers, Project Managers, Technical Marketing Managers, Product Marketing Managers, Developers, QA/Testers, Software Quality Assurance, Human Interface Engineering, Architects, Process Engineers, Production Staff, Marketing Staff, Sales Staff, IT personnel and Tech Support. </li></ul></ul>
    8. 8. Product Development Life Cycle <ul><li>The Product Development process helps efficiently employ and allocate resources. While development requirements vary from one product to another, the product development process can be customized based on a specific project. </li></ul><ul><li>  </li></ul><ul><li>Process, by itself, is a tool that can help smoothen project execution; Process is not the goal, the goal is to ship quality products on time. </li></ul>
    9. 9. Benefits of an Effective Process <ul><li>Changes are controlled systematically: the change is requested, the impact analyzed, and the change implemented. The project scope can be managed, and budgets and schedules can also be kept under control. </li></ul><ul><li>  </li></ul><ul><li>Quality assurance: By setting up processes to eliminate defects in the early stages, projects will not fall into extended test-debug-reimplement-retest cycles. Defects should be tracked during the projects as well as in later product releases. </li></ul><ul><li>  </li></ul>
    10. 10. Benefits of an Effective Process <ul><li>Predictable: Managers and project sponsors need projects to be predictable, to provide progress visibility, and to meet schedules, budgets, and other targets. </li></ul><ul><li>  </li></ul><ul><li>System integration: If the integration of components developed by different developers can be well planned from the beginning of the project, the interfaces between components can be synchronized and aligned. </li></ul>
    11. 11. Phases of Product Development <ul><li>Requirements phase: This is a product planning and business evaluation stage. The project's goal and objectives are established during this phase. </li></ul><ul><li>  </li></ul><ul><li>High-Level Design/Planning phase: This phase involves planning how to construct the product that was approved in the Requirements phase. The team members discuss how to create a concrete framework during this phase. </li></ul><ul><li>  </li></ul>
    12. 12. Phases of Product Development <ul><li>Detailed Design phase: During this phase all departments of the product development group implement the original design. The framework established in the previous phase is refined and updated. </li></ul><ul><li>  </li></ul><ul><li>Construction phase: The activities of this phase are mainly code development, and test case design with a percentage of work spent developing the software product and documentation. </li></ul><ul><li>  </li></ul>
    13. 13. Phases of Product Development <ul><li>Pre-Release phase (Alpha and Beta): While developing a product in the Pre-Release phase, all features have been frozen and all effort is focused on fixing bugs and tuning performance. Many tests are performed during this phase to ensure a high-quality bug-free product is shipped. This is the last verification before the product is finally released. In the Beta phase, the focus is on real-world deployment and testing in real-world conditions. </li></ul>
    14. 14. Phases of Product Development <ul><li>Closure phase: After the product is released the project still must pass this crucial Closure phase. This phase provides a way to conclude the project, and conduct post-mortem meetings (both business and project). These meetings are conducted so in the future the process can be improved upon. In addition, the team preserves all the information and archives all documentation. Future teams working on similar projects can share and learn from this project's experience. </li></ul>
    15. 15. Requirement Phase <ul><li>The first stage in developing a product is identifying what to build during the entire Product Development process, to ensure that we deliver the right product at the end of the project. The project's goal and objectives are established during the Requirements phase. </li></ul><ul><li>  </li></ul><ul><li>The purpose of the Requirements phase is to finalize the requirements for product release. Any change on the requirements thereafter will go through the change control process. </li></ul>
    16. 16. Requirement Phase <ul><li>This is also the period during which the Marketing, the PM, and the implementation team work closely together to figure out what needs to be done, how success will be measured, and the amount of effort that will be required. </li></ul><ul><li>The whole phase should be customer-oriented, and the main activity in this phase should be determining customer requirements (the Market Requirements Document or MRD), and the engineering response to the MRD (the Product Requirements Document or PRD). </li></ul>
    17. 17. Requirement Phase <ul><li>The MRD should include the following: </li></ul><ul><ul><li>Mission statement </li></ul></ul><ul><ul><li>Product road map </li></ul></ul><ul><ul><li>Project objectives </li></ul></ul><ul><ul><li>The results of marketing research and analysis, such as competitive info, market positioning </li></ul></ul><ul><ul><li>Customer requirements </li></ul></ul><ul><ul><li>Product localization requirements </li></ul></ul><ul><ul><li>Product compliance requirements </li></ul></ul><ul><ul><li>Business plan/model for the product </li></ul></ul>
    18. 18. Requirement Phase <ul><li>A PRD should also have an Engineering resource commitment and an estimated schedule. A more accurate and precise schedule will be developed during the project plan, which is generated in the planning and high-level design phase. </li></ul><ul><li>The PRD should have enough detail for engineering to start software design, UI design, and testing. The PRD should describe what a feature looks like, and should have a committed resource allocation and a roughly estimated schedule. </li></ul>
    19. 19. Requirement Phase <ul><li>The review for these documents (MRD/PRD) is very important to enhance the quality of these documents. Although requirements are initially vague and incomplete, a high-quality program can only be built from an accurate and precise understanding of the users' needs. Requirements must be explored and refined to be specific, measurable, accurate and testable. </li></ul>
    20. 20. Project Planning/High Level Design Phase <ul><li>Project planning is essential to the project's success. It provides the basis for visibility of a project status and measurement. Conducting a project without a project plan to follow will result in losing track of the project status and failure to detect early warnings or mistakes that otherwise could have been responded to or resolved. </li></ul>
    21. 21. Project Planning/High Level Design Phase <ul><li>Major milestones in the project plan include: </li></ul><ul><ul><li>MRD approval , PRD approval </li></ul></ul><ul><ul><li>Project kickoff </li></ul></ul><ul><ul><li>Project plan approval </li></ul></ul><ul><ul><li>High-level design approval </li></ul></ul><ul><ul><li>Test plan </li></ul></ul><ul><ul><li>Development plan </li></ul></ul><ul><ul><li>UI freeze </li></ul></ul><ul><ul><li>Feature complete </li></ul></ul><ul><ul><li>Localization kit ready </li></ul></ul><ul><ul><li>Alpha, Beta </li></ul></ul><ul><ul><li>Code freeze </li></ul></ul><ul><ul><li>GM </li></ul></ul>
    22. 22. Project Planning/High Level Design Phase <ul><li>The purpose of the Planning phase is to plan the project and formulate the baseline plan including doing high-level design, breaking down the work into small pieces, estimating project size and schedule, evaluating risks and staffing. Upon entering this phase, the team's focus starts to switch from what to build to how to build, which requires extensive planning and designing activities. </li></ul><ul><li>  </li></ul>
    23. 23. Project Planning/High Level Design Phase <ul><li>This product development phase involves mapping the goals and objectives established during the Requirements phase into a concrete plan. During the High-Level Design phase, all departments have already endorsed the feasibility of the PRD and have committed to the project. They now begin developing the project plans and the High-Level Design. </li></ul><ul><li>  </li></ul>
    24. 24. Project Planning/High Level Design Phase <ul><li>Although no code is generated during this phase, it may seem that the activities performed are actually delaying the real work of the project. However, the reality is quite different. The groundwork for the entire project's success is being laid out. </li></ul><ul><li>  </li></ul><ul><li>The difference between high-level design and detailed design is that while the high-level design identifies the modules and their interrelationships, detailed design deals with the modules themselves. </li></ul><ul><li>  </li></ul>
    25. 25. Detail Design Phase <ul><li>The purpose of the Detailed Design phase is to finalize the design and complete the test plan with test cases. After finishing the product's framework design, the whole product development team goes into the Detailed Design phase. When detailed software design is undertaken, design problems will surface and design changes will be needed. When such changes are made, the design documentation must be updated. </li></ul>
    26. 26. Construction Phase <ul><li>The purpose of the Construction phase is to implement the design stage by stage. At this point, it is assumed all the software requirements have been discussed, considered, and reviewed. When a product reaches this phase, the project team focuses on execution of the plans. </li></ul><ul><li>The activities in this phase are primarily code development, test software development, and the beginning of test case execution, with a percentage of work devoted to the development of the software product and documentation. </li></ul><ul><li>  </li></ul>
    27. 27. Construction Phase <ul><li>The Construction phase can be divided into recurring stages. A wrap-up meeting should conclude every stage to ensure that the criteria that were set are met. The stage wrap-up meeting also serves as a venue for revising the plan and scheduling unfinished tasks. </li></ul><ul><li>  </li></ul><ul><li>If there are indeed changes, the change management process should be used to address the changes. All detected defects should be classified and recorded in the defect tracking system and followed up until the closure. </li></ul>
    28. 28. Pre-release Phase <ul><li>While entering the Pre-Release phase, the focus on the Implementation team should switch from construction to final touches. The goal for the Pre-Release phase is to prepare for the release, thus only the showstoppers will be accepted. </li></ul><ul><li>  </li></ul><ul><li>The purpose of Pre-Release phase is to test and fix the bugs of the product to meet the acceptance criteria. After all the features are coded, the feature complete milestone is met and the project goes into the pre-release phase. </li></ul>
    29. 29. Pre-release Phase <ul><li>In some projects, the period between feature complete and the first alpha build is called pre-alpha. The Pre-alpha phase is mainly fixing the bugs to met alpha quality. Following pre-alpha are two cycles called Alpha and Beta. </li></ul>
    30. 30. Alpha <ul><li>Before Alpha cycle, major functions of the product should be complete while minor functions may still be under development. A product must meet the following criteria to reach Alpha: </li></ul><ul><li>  </li></ul><ul><ul><li>Major product features are complete </li></ul></ul><ul><ul><li>No P1 or P2 bugs </li></ul></ul><ul><ul><li>Rough draft of product documentation should be available </li></ul></ul><ul><ul><li>Basic Release notes should be available </li></ul></ul>
    31. 31. Alpha <ul><li>The focus of the team during the Alpha is to get the product out the door and to eliminate the possibility of showstoppers in the succeeding cycle and phases. Internal testing, features and program code are completed during this cycle. A product is considered to have concluded the Alpha cycle once it completes the entry criteria for the Beta cycle. </li></ul>
    32. 32. Activities During Alpha <ul><li>Tune Performance </li></ul><ul><li>Conduct QA Alpha Test </li></ul><ul><ul><li>Regression Test </li></ul></ul><ul><ul><li>Compatibility Test </li></ul></ul><ul><ul><li>Performance Test </li></ul></ul><ul><ul><li>Vulnerability Assessment </li></ul></ul><ul><ul><li>Volume Test </li></ul></ul><ul><ul><li>Stress Test </li></ul></ul><ul><ul><li>Trend Micro Standards Compliance Verification </li></ul></ul>
    33. 33. Activities During Alpha <ul><li>Conduct Super Lab Test </li></ul><ul><li>Conduct Internal Test Using IT Production Servers </li></ul><ul><li>Complete Documentation </li></ul><ul><li>Develop Package Design </li></ul>
    34. 34. Beta <ul><li>During the Beta cycle, all product features are implemented and code development is stopped. Code freezing begins in this cycle. Only bug fixes are allowed from this point on. </li></ul><ul><li>  </li></ul><ul><li>The focus of the Beta cycle is to release the product to the real world for testing. Beta customers provide valuable feedback about how the product functions in real customer environments. </li></ul><ul><li>  </li></ul>
    35. 35. Beta <ul><li>The Beta plan serves as a guiding policy on objectives of Beta and Beta criteria, to guide the Beta customer recruitment, Beta quality assessment. Before the Beta cycle, the product must meet the following criteria: </li></ul><ul><li>  </li></ul><ul><ul><li>Pass Super Lab testing. </li></ul></ul><ul><ul><li>After two weeks of continuous internal testing, there should be no crashes or serious problems. </li></ul></ul><ul><ul><li>No P1 or P2 bugs. </li></ul></ul>
    36. 36. Closure <ul><li>The purpose of the Closure phase is to release the product and to conclude the experience and lessons from this project. Once the product has passed all testing and has been proven to meet the quality standard defined in the PRD, the Beta Plan, and the Test Plan, it is ready for market release. </li></ul><ul><li>  </li></ul><ul><li>All Product Managers, Project Managers, Developers, Testers, Human Interface Engineers, Build masters, ITs and Tech Support staff have to verify all their tasks have met the release quality standard to ensure the quality release endorsement. </li></ul>
    37. 37. Closure <ul><li>Major Activities </li></ul><ul><ul><li>Endorsement Meeting </li></ul></ul><ul><ul><li>Post-Mortem Meeting/Project </li></ul></ul><ul><ul><li>Archive All Project Data </li></ul></ul><ul><ul><li>Transfer of Information (TOI) </li></ul></ul><ul><li>After the product is released, both the Product Manager and the Project Manager need to hold post-mortem meetings. A post-mortem meeting is a review of the process and a discussion of what improvements could be made. Basically post-mortem deals with the questions, “did we build the system right?” </li></ul>
    38. 38. Project Management – Planning <ul><li>A good planning is a good start of the project </li></ul><ul><li>Include all functional groups and all activities during the development cycle </li></ul><ul><li>Conducts the project kickoff meeting </li></ul><ul><li>Coordinates with the team to break down the project into manageable items </li></ul><ul><li>Assembles project items and inter-dependencies into a project schedule covering all engineering efforts </li></ul><ul><li>Formulates the Project Management Plan. This plan should be discussed, reviewed and revised at the end of each development stage </li></ul>
    39. 39. Project Management – Planning <ul><li>Identifies and resolves project risks </li></ul><ul><li>Schedule actions for risks and potential problems </li></ul><ul><li>Performs resource planning. Allocates engineering resources according to a project’s needs and availability of developers, QA, Human Interface engineers and architects </li></ul><ul><li>Prioritizes project tasks and items </li></ul><ul><li>Setup project objectives and quality attributes </li></ul><ul><li>Setup working model in the project team </li></ul>
    40. 40. Project Management – Risk Management <ul><li>Any exceptions that prevent the project team from reaching the project goal are considered risks, which vary from resource changes/inefficiency, to unavailability of outside dependency, to failure of employment of new technology/algorithm failure, etc. </li></ul><ul><li>Build up risk management committee and schedule regular meetings to continuously identify risks, evaluate impacts, schedule in actions, and plan contingency </li></ul><ul><li>Avoid same problems in previous projects by learning from post-mortem of previous projects </li></ul>
    41. 41. Project Management – Monitoring <ul><li>Docs in planning phase are the baseline for the project </li></ul><ul><li>Use baseline and deliverables (e.g defect reports) to monitor schedule (milestones) slippage, quality deviation, and resources shortage and takes corrective action when necessary </li></ul><ul><li>Verifies deliverables, watch for deviations </li></ul><ul><li>Adjusts (re-prioritize, re-assign, add, etc.) work items and resources to eliminate deviations </li></ul><ul><li>Solves issues and makes trade-off decisions on features, designs, and defects resolutions </li></ul>
    42. 42. Project Management – Monitoring <ul><li>Provides other departments with regular project status reports </li></ul><ul><li>Monitors identified risks </li></ul><ul><li>Ensures the team follow disciplines </li></ul><ul><li>Manages internal and external dependencies </li></ul><ul><li>Maintains a project log for end-of-stage wrap-up and postmortems </li></ul>
    43. 43. Project Management – Status Reporting <ul><li>Not only outside world needs to know the project status, so does every project team member </li></ul><ul><li>Status includes work in all functional groups </li></ul><ul><li>Use milestones as check mark </li></ul><ul><li>Present facts on features (project scope changes), schedule (approaching milestones), quality (defect statistics, execution of test cases, etc.) </li></ul><ul><li>Present issues and resolution actions </li></ul><ul><li>Present risks, mitigation actions, and contingency plans </li></ul>
    44. 44. Project Management – Change Control <ul><li>Every change go through Change Control Process </li></ul><ul><li>Once committed, changes become part of the project </li></ul><ul><li>Modify plans to reflect the changes and let all stakeholders know the changes and ask them to act correspondingly </li></ul><ul><li>Watch for potential risks and problems, and schedule actions for them </li></ul>
    1. A particular slide catching your eye?

      Clipping is a handy way to collect important slides you want to go back to later.

    ×