Week 2 Lecture
Week 2 Lecture
Planning
What is the relevance of planning in your daily lives? What happens when you dont plan?
People
People are the most important element to success Ensure that team roles are well defined as well as communication and coordination between them. Needs and requirements must be clearly defined Select the right System Development Methodology for your team and requirements
Product
Process
Project
Manage the project by setting targets, maintaining development pace, tracking progress, making effective decisions, and conducting a post-mortem analysis.
People
Throwing more bodies at a project will not make it faster to complete Client is not clearly defined, so various clients define conflicting requirements and are wishy-washy Selecting a methodology that the team is not familiar with will cause the team to revert in times of stress A project manager must do more than set deadlines Sustainable pace is key
Product
Process
Project
Project Planning
Just like the system itself, the planning of a software project must be done systematically. An ideal project plan should address the following issues:
Processes and tasks to be performed People to do the work Mechanisms to assess the risks Procedures to ensure the quality of the product Estimation of the cost and effort to be expended Resources and time required to execute the project
Software Scope
An unambiguous and concise scope that will affect the resources, cost, and schedule of the project must be defined at the outset and managed through the course of the project Functions the proposed software will perform Performance and quality standards it will meet Technical and environmental constraints Interfaces the software will interact with Reliability requirements of the software
Resources
After defining initial scope, you must estimate and gather required resources. Human resources: analysts, designers, developers, network & database admins, etc Software resources: Off-the-shelf, Fullexperience, Partial-experience, New Environmental resources: Hardware and Software tools for development
Software Metrics
Project Estimating
Estimating uses empirically derived formulas based on past experience Estimating is important on two levels:
Initial project estimate Development estimates (iterations make this easier)
Estimation models
Software Equations COCOMO: Constructive Cost Model Experience
Tools such as Microsoft Project can help Gantt Charts PERT Charts
Risk Analysis
How do you manage risks in your daily life? Project risk categories
Project Risks Technical Risks Business Risks
Additional Links
Classic planning mistakes http://www.stevemcconnell.com/rdenum.htm