agile_planning.md

Agile Planning

In this lab you will be preparing to develop the first version of the software.

Product Features

These tasks should be carried out on a whiteboard or flipchart.

Start by carrying out a brainstorm of the cool features you could add to the product. Don't worry about how outlandish or advanced these features are, just write them down! Spend around 15 min on this. Write them down on a whiteboard.

1. Describe the feature from the user perspective, don't discuss implementation!
2. Don't be limited by the kit contents, we can find more kit if needed.

Now you need to prioritise these into four categories, add the appropriate letter against each:

1. Must have (what is the minimum you can do to get a product into the hands of the customer).
2. Should have
3. Could have
4. Would be nice to have

Product Roadmap

These tasks should be carried out in a shared MS Word document in MS Teams

1. Now enter all these into a word document on teams, grouped by the four categories above.
2. Within each category place them in priority order.
3. Write each feature out as a User Story. This must include:
   1. A sentence that describes how it will work from the user perspective
   2. A sentence describing the benefit to the home owner.
4. identify the point at which there will be an Minimum Viable Product, the first point at which the system can be released to the end users.

Investigate Agile

These tasks should be carried out in a series of shared MS Word documents saved in a folder called Agile in MS Teams

During the lecture you were introduced to several different agile methodologies. You should investigate and compare these:

1. Scrum
2. Extreme Programming (XP)
3. Dynamic Systems Development Method (DSDM)
4. Crystal Methods
5. Feature-Driven Development (FDD)
6. Lean Development (LD)
7. Adaptive Software Development (ASD)

using the following headings, each member of the team should be assigned one of these methodologies and create a new MS Word document that includes notes, links to useful resources and appropriate diagrams answering the following four questions:

1. What is it called?
2. What is the significance of the name?
3. List three key features that make it different from the others.
4. How can it be employed to improve the quality of the software you produce.

Once this is done, get together as a team to discuss and review your findings.

Finally, create a new MS Word document that places the methodologies in order based on whether your team feel they will make them more effective, explaining and justifying your choice.