Tiger Team SA - Spec Writing & Analysis

See below linked document and detailed task assignments that reflect the roles and responsibilities of the SA's within Tiger Teams in the OLE Development Process. These are Subject Matter Experts (SME) with 50% individual or combined commitments, with either technical or functional expertise in the subject area of the team. The SA is primarily charged with overseeing all aspects of developing specifications, from overseeing user requirements by spec teams, to completing functional requirements documentation (with technical support and training by core team).

Note: "SA" or "Tiger Team Systems Analyst" is the name given to general analysts on the Tiger Teams to distinguish them from the BAs or Business Analysts on the Core Team. In some cases, these are still functional subject matter experts only, while in other cases, the SA does bring specific technical knowledge of coding or the Kuali technology framework (Rice et al).

• Acquisitions/Financial: Select & Acquire Tiger Team (Bob Persing)
• Cataloging: Describe-Manage Tiger Team (M Suranofsky- with SME lead D Herrold)
• Circulation: Deliver Tiger Team (C Case - with SME lead S Miller)
• ERMS: Manage-Entity-Relationship Tiger Team (E Lynema?)
• Implementations/Technical: Systems Integration Tiger Team (N Ma- Core Team)
• Identity Management: Manage-User-Relationships Tiger Team (TBD)
• Subscriptions project: GoKB (D Sweeney- Core Team, with SME lead J Little)

Task Assignments

In the tasks below (except review steps), each shall have linked wiki pages for the required documentation and templates to be used in the completion of technical and functional specs.

6- USER REQUIREMENTS -Spec team & SA

1. Organize and oversee spec writing by spec teams
2. Complete with Spec Team "User Requirements" template
3. Complete with Spec team "Data elements" template
   1. including default values/fields
   2. notes on any progressive disclosure or rules
   3. including noted required fields
4. Assist spec team in annotation and understanding of  "Acceptance criteria" in user requirements
5. Table for roles/permissions
   1. from user requirements,assist 
6. Model for workflow
7. Model for approval steps if any
8. Business rules

8-REVIEW- Tiger Team

1. Review and approve specs
2. Finalize or add Acceptance Criteria- what and how?
3. Note anything out of scope
4. Meet with PM to help determine prioritization
5. Sample data needs identified- given to SA and TC
6. Sample technical integration points culled by TC (ie for APIs, other tech specs needed)

11-CODEABLE SPECS- Once Tiger Team has completed its spec review, and handed off the specs to Project Management in the spec inventory, user stories and tasks will be formally assigned to the project schedule. From that re-prioritization, the SA and BA (with spec team or Tiger Team where needed) complete Functional Specs/Requirements docs for coding

1. UI Rice 1.0/KFS e-doc template
2. UI Rice 2.0/full web app template
3. Roles/permissions added
4. Rice workflows, approvals finalized
5. Acceptance Criteria reviewed and completed?
6. Business Rules
7. KRMS Rules
8. Completion of full Functional and non-Functional specs

12, 17- HANDOFFS & REVIEWS- SA, Spec Team, Tiger Team

16- TEST SCRIPTS- once development is begun, then SA and Spec Team work with QA Manager/team to develop Test Scripts for each set of coded specs (note: some user stories in initial spec writing may have been adapted to Kuali technology OR been combined to code core functions).

23, 25-26 TESTING: Spec Team, SA, Tiger Team

(iterative) Gap Analysis: SA, Tiger Team 

Summary: Business Rules

(insert table/link)

Summary: Workflows, Routing

(insert table/link)

Summary: Roles, Permissions

(insert table/link)