-
Notifications
You must be signed in to change notification settings - Fork 1
Delivery: Requirements
This is the delivery of the Requirements. This will be used as the input to our design and planning process.
The scope of the Requirements is the business domain, up to the boundary technology; if you need help with terms like this meet with us as soon as you can
This is the top-level document of your delivery. If you haven't yet done so, create a folder 'deliveries' in the top level of your project. create a folder:
delivery_14_11_2017
create a markdown file in the folder:
requirements.md
In the file:
- Title: Project: Team name
- Brief: Link to brief
- Introduction: introduce the project and a short summary of the requirements
- Budget: state the total effort budget in hours. Link to the checked-in spreadsheet in GitHub
- Features: link to the features board
- Investigations: link to the investigations board
- Implementations: link to the implementations board
- Update the spreadsheet with your team's current commitment
- Check it in to your project on GitHub
As complete a description of our Minimum Viable Product as possible:
- UI
- Behaviour
- Data Model For each Feature, link to an investigation, if needed. For each Feature, link to an implementation statement, if needed. For UI, you may need to describe UI elements. If so, please use Evolus Pencil. You can attach descriptive wireframes pics to your features. Don't forget to check your pencil files into your repo!
The investigations board is relevant throughout the project, so is never considered complete! Contains the following lists:
- Todo: An up-to-date list of investigations needed, prompted by describing the system in the Features board.
- Pending: A list of investigations currently being performed. Each investigation needs an assigned person, and an estimate of the time taken for that person to do it.
- Done: a list of completed investigations. Each investigation needs a note of the time taken to do it, a conclusion and links to evidence (source code, etc).
An up-to-date list of implementation statements.
e.g.
| Ionic / Cordova |
|---|
| Reason: Client request |
e.g.
| Stored Queue |
|---|
| Reason: need to store data in files for upload. |
| Link: Link to Investigation |
We use the features board to be able to describe our MVP in a way which will allows us to understand how much effort it will take to produce, AND evaluate what we may need to sacrifice, to guarantee a result. The Requirements delivery is the first step on the way to being able to do this. It's a complete description of the system we want: UI, behaviour and models needed to represent data it may manipulate.
We use the Implementations board to make statements about decisions we have taken to use a certain technology, or implement a feature in a certain way.
The Investigations board backs the implementations decisions we have made, with real, targeted investigations which focus on a specific problem and don't waste time.
The Investigations board points to knowledge acquired during investigations so we can easily refer to them in future.
Allows us to understand how much effort there is available to apply to the project and how much is yet to be known, so we can guide you in your design and planning.
Defining the requirements is a collaborative process with your client. If you haven't met with us yet, please do!.