Why Change Fails? The short answer: politics Many project problems are bigger than just your project You have to make changes to the way people in your organization work Your ideas on how to improve the way work is done will not always be evaluated rationally Change is Uncomfortable Nobody likes to think that they […]
Unit 8: Software Testing
Quality Quality means “conformance to requirements” The best testers can only catch defects that are contrary to specification. Testing does not make the software perfect. If an organization does not have good requirements engineering practices then it will be very hard to deliver software that fills the users’ needs, because the product team does not […]
Unit 7: Design and Programming
Review the Design Once the SRS has been approved, implementation begins. Programming teams have many options: The programmers can simply start building the code and create the objects and user interface elements. Designers can build a user interface prototype to demonstrate to the users, stakeholders and the rest of the team. Any code used to […]
Unit 6: Software Requirements
Software Requirements Software requirements are documentation that completely describes the behavior that is required of the software-before the software is designed built and tested. Requirements analysts (or business analysts) build software requirements specifications through requirements elicitation. Interviews with the users, stakeholders and anyone else whose perspective needs to be taken into account during the design, […]
Unit 5: Reviews
When are reviews needed? A review is any activity in which a work product is distributed to reviewers who examine it and give feedback. Reviews are useful not only for finding and eliminating defects, but also for gaining consensus among the project team, securing approval from stakeholders, and aiding in professional development for team members. […]
Unit 4: Project Schedules
What is a project schedule? The project schedule is a calendar that links the tasks to be done with the resources that will do them. Before a project schedule can be created, the project manager must have a work breakdown structure (WBS) and estimates. The schedule is part of the project plan Scheduling concepts: Effort […]
Unit 3: Estimation
What is estimation? The project manager must set expectations about the time required to complete the software among the stakeholders, the team, and the organization’s management. If those expectations are not realistic from the beginning of the project, the stakeholders will not trust the team or the project manager. Elements of a Sound Estimate To […]
Unit 2: Tools and Techniques
Why do software projects fail? People begin programming before they understand the problem Everyone likes to feel that they’re making progress When the team starts to code as soon as the project begins, they see immediate gains When problems become more complex (as they always do!), the work gets bogged down or slowed down In […]
Unit 1: Software Project Basics
Software Project A Software Project is the complete procedure of software development from requirement gathering to testing and maintenance, carried out according to the execution methodologies, in a specified period of time to achieve intended software product. Need of software project management Software is said to be an intangible product. Software development is a kind […]