Internal Portal

Purpose Statement: 

1. Get a Purpose Statement early doors 

   1. What they want the system to do, how it will work and operate. (system requirements)

   2. Get a core team who are involved in all calls/discussions

   3. Create the Epic case

   4. Flow charts possibly needed here in some scenarios

   5. Scenario Plan discussions

Define the terms for the project (ie ‘Saved Responses’ in RfP Qs) then unless there is good reason, we stick to these. 

Development team thought-shower

1. What the system should and shouldn’t do

2. Scenario planning - ensure all areas are covered

3. Around step 3 we will begin to create the cases within the Epic

4. Around this time, come up with an expected delivery date

Wireframing

1. A quick method to discard anything we deem impractical and get a flow of the process

Designing

1. John: “should be done in greyscale at first so we can sort out the functionality, then we can add colour’

2. Designs should be in HTML that we can give to the business and we can ‘show them’ the process and what happens when you navigate through the changes

3. John/Hainan/Devs could provide the ‘vanilla’ HTML that would be used and then design team could add in the extra interactivity

4. Would also provide any changes to a Design Library

5. Once we have a prototype wireframe ‘system’ - we can demo it to get feedback for further review & improvements.