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