Skip to content

PROBLEM STATEMENTS

Writing activity

Writing activity

Writing activity

The problem statements are used to state clearly the end-goal that will be achieved by completing the development process.

They will constrain the process of development so that bloat or creep can be avoided. If something does not fit with the identified problem, it shouldn't be included.

They can be easily created alongside the client's direct input so that their needs are addressed and fulfilled.

They should be brief and straightforward. The structure is very simple:

- How might we …..
- For ...
- So that …
- Taking into account that ...

For example,

For the project overall

  • How might we provide a web-based solution
  • For the Health Advisory Group
  • So that they can provide health information, advice, and guidance to clients
  • Taking into account that access will be restricted to registered users.

For a single process, such as the login sequence

  • How might we provide an authentication system for the app
  • For different user type groups
  • they can be authorised to complete specific tasks
  • Taking into account that the users may need to recover forgotten credentials.

For a feature

  • How might we provide current air quality information
  • For end users
  • So that they can identify risk conditions
  • Taking into account that they must be able to specify a location.

User stories - Example from the Exemplar Portfolio

User Stories