TwoWeekStatusReport.ppt

Final Status Report Sonali Pagade Nibha Dhagat David Ziman Reginald Bradshaw II Sebastian Schagerer Janet Xu Phan Purpose for Today’s Meeting Report on progress made since inception Review: Team Organization, Brain Storming, Vision Document Show past few weeks progress: Standish Report Use Case, Structural, and Behavioral Diagrams Non Functional Requirements, Mockup Project Deliverables To Do: Finish SRS Peer ratings Project Evaluation Completed: Vision Document Project Plan Draft Status Report 1 2 Final Status Report Organizing the Team Exchanged contact information Setup Yahoo! Group for communication and file sharing/storage Group Meetings to discuss project plan Brainstorming Session Brainstorming for product needs and wants Brainstorming session with appropriate stakeholders Revised Brainstormed Ideas Accepted or Rejected wants/needs Created a comprehensive Feature list Vision Document Sections 1-7 1. Introduction 2. Positioning Section 3 - Stakeholders Understand who is involved in the current business process Understand who will be involved in the improved process Identify features with Stakeholders for traceability Vision Document Sections 4-8 4. Product Overview 5. Product Features 6. Constraints 7. Quality Ranges 8. Precedence and Priority Vision DocumentSections 9-10 9. Other Product Requirements 10. Documentation User Manual Online Help Labelling and Packaging Appendix A. Feature Attributes Status, Benefit, Effort, Risk, Stability, Target Release, Assigned To, Reason Standish Report Factors Contributing to Project Success According to Standish Report: 1. Executive Management Support 2. User involvement 3. Experienced Project Manager 4. Clear Business Objectives 5. Minimized Scope 6. Standard software Infrastructure 7. Firm Basic Requirements 8. Formal Methodology 9. Reliable Estimates 10. Other The cost of incorrect, misunderstood, and not agreed upon requirements affects the customers and developers in terms of time, money, and lost oppo