Software Engineering - Project Planning | 26 November | 7:30 PM

TL;DR

This content provides an overview of software project planning and management, discussing the characteristics of software projects, stakeholders, project failures, and the W5HH approach.

Transcript

do hello everyone good evening to you all we are back in our software engineering course and today's topic is software project planning so today we will cover uh topics uh on project planning let me put it on slideshow yeah that's better so we will detail with some of the topics in software project planning we'll go we will discuss some of the basi... Read More

Key Insights

• 📽️ Software projects have unique characteristics that make their planning and management challenging.
• ❤️‍🩹 Stakeholders in software projects can vary from senior managers to end-users, each with different levels of influence.
• 🧑‍🏭 Project failures can occur due to various factors, including poor requirement understanding, unrealistic deadlines, and technical difficulties.
• 📽️ The W5HH approach provides a structured framework for software project planning and management.

Questions & Answers

Q: What are the key characteristics that differentiate software projects from other engineering projects?

Software projects have characteristics like visibility (unseen progress until completion), conformity (specification derived from human perception), ability to change (flexibility to make changes until delivery), complexity (emerging technology and varying skills required), and return on investment (cannot be accrued until complete).

Q: What are the types of stakeholders that influence software projects?

Software projects have three types of stakeholders: external stakeholders (senior managers, business managers, customers), internal stakeholders (practitioners, technical managers), and support staff (vendors, management staff).

Q: Why do software projects fail in planning and management?

Software projects can fail in planning and management due to reasons such as poor requirement understanding, poorly defined scope, inability to manage changes, underestimation of effort and unrealistic deadlines, unpredictable and predictable risks, lack of sponsorship, technical difficulties, and managerial or practitioner problems.

Q: What is the W5HH approach in software project planning and management?

The W5HH approach stands for Why, What, When, Who, Where, and How. These questions help project managers in software project planning and management by addressing the objectives, schedules, responsibilities, management and technical approaches, and resource requirements.

Summary & Key Takeaways

• Software projects have unique characteristics, including visibility, conformity, ability to change, complexity, and return on investment. These characteristics make software project planning and management challenging.

• There are various types of stakeholders in software projects, including senior managers, business managers, customers, end users, practitioners, and support staff.

• Project failures can occur due to reasons such as poor requirement understanding, unrealistic deadlines, unforeseen risks, sponsorship issues, technical difficulties, and managerial problems.