CS615 Software Project Management Assignment 1 for Fall 2026 is built around a university learning management system (LMS) project. A team of eight has six months and a budget of Rs. 5 million to build the LMS, but the project is in trouble: requirements are unclear, roles are confused, there is no plan or schedule, work is duplicated while important tasks are ignored, and change requests arrive without any control. The assignment asks for the problems and their fixes, the four Ps of project management, a recommended SDLC model, and a plan for managing scope, time and cost.
The solution file linked below covers all four questions in full. It explains each problem with the action the project manager should take, applies the four Ps to this exact project, justifies an Agile approach over Waterfall, and shows how to balance the triple constraint without sacrificing quality.
What Does the Solution File Cover?
What Are the Five Project Problems and Their Fixes?
First, unclear requirements: without agreed requirements the team cannot design, estimate or test the LMS, and rework is likely. The fix is interviews and workshops with university stakeholders, prototypes, a Software Requirements Specification (SRS), and customer approval of that SRS as the baseline. Second, confused roles and responsibilities: nobody knows who owns which work, so decisions and accountability are unclear. The fix is a defined team structure, a responsibility (RACI) matrix, and a kick-off meeting to explain the roles.
Third, no project plan or schedule: there are no milestones, estimates or deadlines to track progress against the six-month limit. The fix is a full project plan with a Work Breakdown Structure (WBS), effort and cost estimates, a Gantt chart schedule with a critical path, milestones and a risk plan. Fourth, duplicated and ignored tasks: effort is wasted on the same task while important tasks remain undone. The fix is breaking work into WBS tasks, assigning each task to one owner, tracking status on a task board, and holding short regular progress meetings. Fifth, uncontrolled change requests, or scope creep: extra features increase cost and delay delivery without approval. The fix is a change control process with a written request, impact analysis on time and cost, approval by a change control board, and updating of the baseline if accepted.
How Do the Four Ps Apply to This Project?
People come first because a project succeeds or fails mainly through its team. The eight-member team and the university stakeholders must be managed with the right skills, clear roles, motivation and regular customer communication. Product means the LMS itself: course registration, lecture videos, quizzes, assignment submission and results, with objectives, scope and quality expectations agreed before work starts. Process means choosing a suitable development framework with defined activities such as requirements, design, coding, testing and reviews, plus configuration management for handling changes. Project covers planning, monitoring and controlling the work within six months and Rs. 5 million, including schedule, budget, risk management and early correction of deviations. A related design approach is the CS605 Assignment 1 solution on the Iterative Model, and the requirements side connects to the CS504 Assignment 1 solution on use case modeling.
Which SDLC Model Is Recommended and Why?
The recommended model is iterative and incremental development using an Agile approach such as Scrum. Requirements are unclear and changing, and Agile refines them through short iterations and regular customer feedback, which a linear model cannot do. The LMS divides naturally into modules, so registration, videos, quizzes, assignments and results can be delivered in increments and the university sees working software early. With a prioritised product backlog, the most important features are built first, so if time runs short the least important features can be postponed instead of missing the deadline. New requests go to the backlog, get evaluated and are scheduled in a later iteration, which keeps changes controlled. A team of eight suits Scrum, and testing in every iteration finds defects early. Waterfall is not suitable because it needs all requirements fixed in advance and delivers working software only at the end, so late changes would be costly. One condition matters: the university should appoint a representative who can give regular feedback and decisions.
How Are Scope, Time and Cost Balanced?
Scope, time and cost form the triple constraint: changing one affects at least one of the others, and quality suffers if they are not balanced. The solution shows six practices: define and baseline the scope in writing with a WBS, estimate and plan realistically with milestones and a contingency reserve, prioritise features (Must have, Should have, Could have) so essential LMS functions are protected first, control changes with impact assessment and formal approval, monitor progress and spending against the plan and report to stakeholders, and protect quality by never cutting testing to save time or money. When scope increases, the customer must accept more time, more budget, or the removal of lower-priority features.
How Do You Download the Solution File?
You can download the complete solution file from Google Drive using the link below. Read the five problems table first, then the four Ps, then the SDLC reasoning, and make sure you can explain each part in your own words before submitting. Also check your work against the exact assignment file on VULMS, since question wording can vary.
Frequently Asked Questions
What is the triple constraint in project management?
The triple constraint is the balance between scope, time and cost. Changing one of them affects at least one of the others, and if they are not balanced, quality suffers. For example, adding features without more time or budget forces the team to cut corners, usually in testing.
Why is Agile better than Waterfall for this LMS project?
Waterfall needs all requirements fixed in advance and delivers working software only at the end. This LMS project has unclear and changing requirements, a fixed six-month deadline and a fixed budget, so an iterative Agile approach fits better: it refines requirements each iteration, delivers modules early, and lets lower-priority features slip instead of the deadline.
What is a RACI matrix?
A RACI matrix documents who is Responsible, Accountable, Consulted and Informed for each task. It removes role confusion because every team member can see exactly who owns each piece of work and who makes the decisions.
What is scope creep and how is it controlled?
Scope creep is the uncontrolled addition of extra features, which increases cost and delays delivery. It is controlled with a change control process: every new request is written down, its impact on time and cost is analysed, a change control board approves or rejects it, and the baseline is updated only for accepted changes.
Last updated: November 2026.
