ProcessA

142 views

Published on

Published in: Technology, Business
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
142
On SlideShare
0
From Embeds
0
Number of Embeds
3
Actions
Shares
0
Downloads
0
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

ProcessA

  1. 1. ProcessThoughts points
  2. 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. 3. InternalReleases 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. 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 / devpartnership and using BDD? Do we need a Quick QA process / dev demo to test before card ismoved to ready for test?
  5. 5. How do wedeal withbugs? Do they just get played onto the board as items ? How are bugs rated and how will they be weighted against featurework? -TFS. – discuss
  6. 6. Requirements Epics? [Format?] Feature?[Format?] Storys ?[Format?] Test Plans? [Format?] What is done? Discuss
  7. 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 onTFS and Process? [Document]

×