# Check List

*mark stuff as complete once they are done on the project plan doc*

## Front page
- [x] Does it contain the name of the project?
- [x] Does the product have a clear, catchy name?
- [x] Does the front page contain the name of the group and the names of the group
members?
- [x] Does it contain the date of delivery?
## Lay-out
- [x] Does the plan contain a table of contents with page numbers?
- [x] Are chapters numbered?
- [x] Are page numbers present on the pages?
- [x] Are chapters clearly marked?
## Language
- [x] Is the writing style clear and concise?
- [ ] Has the document been checked for spelling and grammatical errors?
- [x] Has a business-like writing style been used? No use of pronouns?
- [x] Are sentences not abundantly long?
- [x] Is the project plan clearly pointedly written, with a clear structure and
enumerations?
- [x] Are unknown concepts introduced before being used?
## Project result
- [x] Is it clear what the end result of the project will be? Is it clearly specified how the
product will function and what the software will look like?
- [x] Is it clear what the requirements are? Is it clear what part of the project is essential
and what possible expansions are? What is not in the project’s scope?
- [x] Are all intermediate results defined?
- [x] Are any events, designs, reports and such included in the project result definition?
## Project organisation
- [x] Is the contact information for all project members in the project plan?
- [x] Are all positions in the project group appointed?
- [x] Is the availability of all project members considered? (Holidays, weddings, etc.)
- [x] Have clear agreements been made regarding availability and performance?
- [x] Have all stakeholders to the project been mentioned?
- [x] How and when is communication with the ‘client’ happening?
- [ ] Is a time sheet available?
- [x] Is it clear where documents and project results will be stored?
- [x] Is the planning realistic?
- [x] Are all intermediate deadlines included in the planning?
## Scrum
- [x] Is there a Defintion Of Done, i.e. is clear when a story can be burned?
- [x] Does the product backlog contain sufficient stories, so that it contains at least 5
stories per person per sprint?
- [ ] Are most stories of approximately equal size?
- [ ] Have you prevented any stories that make up more than 30% of a story?
- [x] Are story formulated from a user’s perspective and are they in the form ‘As a …, I
want …, so that …’?
- [x] Is it clear for every user story on the sprint backlog what should happen?
- [ ] Is there a how-to-demo that is not up to interpretation?
- [ ] Has the backlog been prioritized by the product owner?
- [ ] Is the velocity in sprint 1 determined realistically and substantiated?