CampusLearn
← BIT 302 Software Engineering

The Software Lifecycle and Agile Methods

Notes

Lifecycle activities The software development lifecycle is the set of activities used to conceive, build, operate and retire software. Requirements work establishes the problem and expected behaviour; design plans the solution; implementation creates executable code; testing evaluates it; deployment releases it; maintenance adapts it after release. These activities are connected rather than isolated paperwork stages. A sequential approach can suit stable requirements and formal approvals, but late feedback can make change expensive. Iterative development revisits activities repeatedly so that assumptions are checked before the entire system is complete. Agile delivery and feedback Agile development emphasises working software, collaboration and responsiveness to change. Scrum organises work into timeboxed iterations called sprints, with a prioritised product backlog and an agreed sprint goal. A product owner orders desired outcomes, developers create the increment, and a Scrum Master supports effective practice. Acceptance criteria describe observable conditions for accepting a feature. A definition of done establishes shared quality expectations across features. Reviews gather feedback on the product, while retrospectives improve the working process. Agile still requires documentation, architectural thinking and realistic capacity planning. Practical example A Nairobi e-commerce startup plans a two-week sprint with four developers. Each has ten working days, but support duties consume two days per person, leaving 4 times 8, or 32 developer-days. The team estimates checkout at 12 days, delivery tracking at 10 and refund automation at 14. All three require 36 days, exceeding capacity by four. Choosing checkout and tracking uses 22 days and leaves ten for testing, integration and uncertainty. At the review, customers report unclear delivery statuses, so the product owner reprioritises improvements. Story points, if used instead of days, represent relative effort rather than guaranteed working hours.

Quiz

1. A sprint has capacity for 32 developer-days and proposed work totals 36. What is the soundest response?

2. Which meeting primarily examines how the team can improve its working process?

3. What does a definition of done provide?

Sign in to submit and securely grade your quiz.