Development Documents 2: Coding your MVP
1. Start to build your MVP.

2. Content Strategist to co-ordinate documents uploaded into Portfolio for submission

3. IXD (Interaction Designer) to co-ordinate submission on Bitbucket on a bitbucket.io site

Specific details for how teams are to do this are outlined below.

1. Responsibilities (Content Strategist)

Outline who is doing what in detail to show how the team is managing this work.

· Add to the document ‘Development Responsibilities’ with your names, team name & roles are included

· Provide the project structure developed in class week 7

· Outline who is co-ordinating what, why and how the team is contributing to each task. This information should match with the work done.

· Upload the ‘Development Responsibilities’ document in Portfolio page

2. Code your MVP

Build your MVP (IXD to co-ordinate)

Preparation

i. Update a diagram your MVP ( eg interaction map or hierarchy diagram)

ii. Set up your Bitbucket repository to match the structure developed

Development

Code some parts of the MVP and regularly commit your work to your Team Bitbucket repository with meaningful commit messages:

i. Setup the directory structure for HTML, CSS, JS, Images and other resources

ii. Create necessary html, css and JS files and work on these

iii. Commit this to your team bitbucket account for your project

iv. Run some tasks with some users and collect feedback. If you have completed your ethics and had it approved, you can do surveys and collect quotes, otherwise you can only comment from what you observed

v. Each team member must commit some javascript/html and css to get a team mark!

Submission
1. MVP

Submit (Either Content strategist or IXD can upload it, decide yourself)

a. Link to the Team live repository site with your code

b. Link to portfolio with summary document Development Sprint 2 linked to:

i. Development Responsibilities document,

ii. Diagram of MVP,

iii. Links to Documents on Teams

c. In your Development Documentation 2 explain:

i. W3C Compliance report

ii. Results of user testing

iii. What you have or will do as result of tests

1