Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 30 Next »

  

Under Construction. To be updated to reflect new OLE Development Process.

The goal of the checklist, when complete, is to guide the overall specification process: from initial User Requirements with Spec teams full circle through testing, and any iterative gap analysis. SME Teams and the Project Team may utilize this to manage processes and workflows around spec-writing (optional tool for managing work and spec progress by SA/SME Team Systems Analyst).

Goals/Objectives

The following is a detailed checklist for completing functional specifications, to ensure completeness of documentation, and full understanding of library requirements for:

  1. Functionality/functional overview
  2. Workflows
  3. Data elements, data flows
  4. Permissions
  5. Business Rules/Parameters
  6. E-doc Routing or approvals/Workflow
  7. KRMS/ advanced business rules
  8. Acceptance criteria and testing scripts
  9. User interface wireframes, navigation
  10. Search

Deliverables

The specific deliverables expected of functional spec teams are:

  1. Develop...
  2. Document ...
  3. Test ...
  4. Communicate...
  5.  

Timeline

Phase

Tasks

Assigned to:

Start Date

Due Date

Status

Phase 1 - Planning

Task 1 - Organize Team / Meetings

 

 

 

 

 

Task 2 - Identify Goals / Deliverables

 

 

 

 

 

Task 3 - Establish Timelines

 

 

 

 

 

 

 

 

 

 

Phase 2 - Drafting

Task 1 - Research / Analyze

 

 

 

 

 

Task 2 - Write / Document

 

 

 

 

 

Task 3 - Develop / Acceptance Criteria

 

 

 

 

 

Task 4- List/define data elements

 

 

 

 

 

 

 

 

 

 

Phase 3 - Reviewing

Task 1 - Present / Communicate

 

 

 

 

 

Task 2 - Implement / System Test

 

 

 

 

 

Task 3 -

 

 

 

 

 

 

 

 

 

 

Final Phase- Deliverable Package

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 
0%

Spec Checklist

  1. handler

    (check) Completing Functional Specs Status Roadblocks Notes

    Priority MEDIUM
    chris.case
    N/A
  2. handler

    Preparation

    Priority MEDIUM
    nroggeve
    N/A
  3. handler

    1. Roadmap to user stories (scope team)

    Priority MEDIUM
    nroggeve
    N/A
  4. handler

    2. Team formed (SME Team drafts)

    Priority MEDIUM
    N/A
  5. handler

    3. SOW prepared-

    Priority MEDIUM
    N/A
  6. handler

    a. how we're changing this process in OLE;

    Priority MEDIUM
    N/A
  7. handler

    b. limits or dependencies for current task

    Priority MEDIUM
    N/A
  8. handler

    c. timeline/due dates

    Priority MEDIUM
    N/A
  9. handler

    4. user stories prepared for spec team

    Priority MEDIUM
    N/A
  10. handler

    5. Spec team onboarding

    Priority MEDIUM
    N/A
  11. handler

    6. Critical dependencies, building blocks, rice services begun to be identified (SME Team-TC+analyst+core)

    Priority MEDIUM
    N/A
  12. handler

    Spec Kickoff

    Priority MEDIUM
    N/A
  13. handler

    1. Share above and reference documents

    Priority MEDIUM
    N/A
  14. handler

    2. Demo relevant to-date-coding for task

    Priority MEDIUM
    N/A
  15. handler

    3. Intro to tools

    Priority MEDIUM
    N/A
  16. handler

    4. Spec team lead w/ SME Team analyst support to lead

    Priority MEDIUM
    N/A
  17. handler

    5. TC in 1st call- begin drafting list APIs, technical challenges or required investigations

    Priority MEDIUM
    N/A
  18. handler

    6. Review, extend SOW

    Priority MEDIUM
    N/A
  19. handler

    7. Evaluation of user stories assigned- into critical or linear path: discussion

    Priority MEDIUM
    N/A
  20. handler

    8. Divide-and-conquer: assignments, due dates

    Priority MEDIUM
    N/A
  21. handler

    9.  

    Priority MEDIUM
    N/A
  22. handler

    Spec-writing

    Priority MEDIUM
    N/A
  23. handler

    1. Draft narratives

    Priority MEDIUM
    N/A
  24. handler

    2. Define glossary of library terms used in narratives

    Priority MEDIUM
    N/A
  25. handler

    3. List and define data elements and attributes in worksheet template

    Priority MEDIUM
    N/A
  26. handler

    4. List key workflows and alternate paths

    Priority MEDIUM
    N/A
  27. handler

    5. Annotate critical business rules

    Priority MEDIUM
    N/A
  28. handler

    6. User roles and permissions (access)

    Priority MEDIUM
    N/A
  29. handler

    7. Approval process (routing)

    Priority MEDIUM
    N/A
  30. handler

    8. Wireframes, UI

    Priority MEDIUM
    N/A
  31. handler

    a. Balsamiq

    Priority MEDIUM
    N/A
  32. handler

    b. Templates TBD

    Priority MEDIUM
    N/A
  33. handler

    c. IU UX

    Priority MEDIUM
    N/A
  34. handler

    d. F2F workshops

    Priority MEDIUM
    N/A
  35. handler

    9. Acceptance criteria (simple)

    Priority MEDIUM
    N/A
  36. handler

    Next steps;

    Priority MEDIUM
    N/A
  37. handler

    1. specs translated to jira tasks/tickets

    Priority MEDIUM
    N/A
  38. handler

    2. key parts of specs into technical documents

    Priority MEDIUM
    N/A
  39. handler

    3. SME team review of specs

    Priority MEDIUM
    N/A
  40. handler

    a. Out of scope

    Priority MEDIUM
    N/A
  41. handler

    b. Remaining questions

    Priority MEDIUM
    N/A
  42. handler

    c. General agreement

    Priority MEDIUM
    N/A
  43. handler

    4. SME Team analyst leads spec completion with help from core team

    Priority MEDIUM
    N/A
  44. handler

    5. Test scripts authoring begun

    Priority MEDIUM
    N/A
  45. handler

    6. SME Team, TC reevaluates for APIs, technical integrations- writes specs on technical gaps

    Priority MEDIUM
    N/A
  46. handler

    7. Documentation/translations made available to spec, tiger, core team- any/all review or comments

    Priority MEDIUM
    N/A
  47. handler

    Developer Handoff

    Priority MEDIUM
    N/A
  48. handler

    1. review technical specs and reference materials

    Priority MEDIUM
    N/A
  49. handler

    2. update or clarify jira

    Priority MEDIUM
    N/A
  50. handler

    3. Coding

    Priority MEDIUM
    N/A
  51. handler

    Iterative review

    Priority MEDIUM
    N/A
  52. handler

    1. Coding begun, iterative clarifications (HTC, analyst)

    Priority MEDIUM
    N/A
  53. handler

    2. 50% code review with spec team

    Priority MEDIUM
    N/A
  54. handler

    3. Code complete-

    Priority MEDIUM
    N/A
  55. handler

    a. Offshore handoff to onshore lead

    Priority MEDIUM
    N/A
  56. handler

    b. Onshore review and move to testing

    Priority MEDIUM
    N/A
  57. handler

    c. Technical testing- core team

    Priority MEDIUM
    N/A
  58. handler

    d. User testing

    Priority MEDIUM
    N/A
  59. handler

            i.    Scripts

    Priority MEDIUM
    N/A
  60. handler

           ii.    Gap analysis vs good enough

    Priority MEDIUM
    N/A
  61. handler

          iii.    Enhancements and bug-fixes into jira

    Priority MEDIUM
    N/A
  62. handler

    SME Team quarterly review

    Priority MEDIUM
    N/A
  63. handler

    1. Open, new jira

    Priority MEDIUM
    N/A
  64. handler

    2. Out-of-scopes

    Priority MEDIUM
    N/A
  65. handler

    3. Gap analysis

    Priority MEDIUM
    N/A
  66. handler

    4. prioritization

    Priority MEDIUM
    N/A
  • No labels

Operated as a Community Resource by the Open Library Foundation