1. Process
Thoughts points

2. Iterations
 How long should they be ?
 How do we plan for them and cost the work ?
 Test
 Dev
 Who needs to be involved in the costing ?

3. Internal
Releases
 How many iterations should we have to a release ?
 Should we have a retrospective per release ?
 Do we have a internal Demo platform to host release product on ?
 Do we show case?
 If we show case who to?
 When?

4. Test
 Do we have a QA /Test environment ?
 How do we release on to that environment?
 What doTest need from dev when we do a release?
 Are we using automation ?
 Is automaton going to run on the nightly?
 Do we have time / or do we want to consider a test / dev
partnership and using BDD?
 Do we need a Quick QA process / dev demo to test before card is
moved to ready for test?

5. How do we
deal with
bugs?
 Do they just get played onto the board as items ?
 How are bugs rated and how will they be weighted against feature
work?
 -TFS. – discuss

6. Requirements
 Epics? [Format?]
 Feature?[Format?]
 Story's ?[Format?]
 Test Plans? [Format?]
 What is done?
 Discuss

7. End product
 Defined rough iteration / release process [Document]
 Defined interaction points between Dev andTest [Document]
 Defined how we release [Document]
 Defined how we communicate and deliver back to the business
[Document]
 Product road map ? Start thinking about.
 Onboarding discussions around developer pack , and guidence on
TFS and Process? [Document]