Page Comparison

(check)	Completing Functional Specs	Status	Roadblocks	Notes
				
	Preparation			
	1. Roadmap to user stories (scope team)			
	2. Team formed (Tiger Team drafts)			
	3. SOW prepared-			
	a.  how we're changing this process in OLE;			
	b. limits or dependencies for current task			
	c. timeline/due dates			
	4. user stories prepared for spec team			
	5. Spec team onboarding			
	6. Critical dependencies, building blocks, rice services begun to be identified (TT-TC+analyst+core)			
				
	Kickoff Spec team			
	1. Share above and reference documents			
	2. Demo relevant to-date-coding for task			
	3. Intro to tools			
	4. Spec team lead w/TT analyst support to lead			
	5. TC in 1st call- begin drafting list APIs, technical challenges or required investigations			
	6. Review, extend SOW			
	7. Evaluation of user stories assigned- into critical or linear path: discussion			
	8. Divide-and-conquer: assignments, due dates			
	9.  			
				
	Spec-writing			
	1. Draft narratives			
	2. Define glossary of library terms used in narratives			
	3. List and define data elements and attributes in worksheet template			
	4. List key workflows and alternate paths			
	5. Annotate critical business rules			
	6. User roles and permissions (access)			
	7. Approval process (routing)			
	8. Wireframes, UI			
	a. Balsamiq			
	b. Templates TBD			
	c. IU UX			
	d. F2F workshops			
	9. Acceptance criteria (simple)			
				
	Next steps;			
	1. specs translated to jira tasks/tickets			
	2. key parts of specs into technical documents			
	3. Tiger team review of specs			
	a. Out of scope			
	b. Remaining questions			
	c. General agreement			
	4. TT analyst leads spec completion with help from core team			
	5. Test scripts authoring begun			
	6. TT TC reevaluates for APIs, technical integrations- writes specs on technical gaps			
	7. Documentation/translations made available to spec, tiger, core team- any/all review or comments			
				
	Developer Handoff			
	1. review technical specs and reference materials			
	2. update or clarify jira			
	3. Coding			
				
	Iterative review			
	1. Coding begun, iterative clarifications (HTC, analyst)			
	2. 50% code review with spec team			
	3. Code complete-			
	a. Offshore handoff to onshore lead			
	b. Onshore review and move to testing			
	c. Technical testing- core team			
	d. User testing			
	                                                 i.    Scripts			
	                                         ii       ii.    Gap analysis vs good enough			
	                                        iii      iii.    Enhancements and bug-fixes into jira			
				
	Tiger Team quarterly review			
	1. Open, new jira			
	2. Out-of-scopes			
	3. Gap analysis			
	4. prioritization