TFTM Work Plan

From IDESG Wiki
Revision as of 04:04, 28 June 2018 by Omaerz (talk | contribs) (20 revisions imported: Initial Upload of old pages from IDESG Wiki)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search

Template:TFTMNavBar Template:TFTMDRAFT The High Level Work Plan wiki section contains the highest level of activity organization.

A Word About Words in this section

A Work Stream is a collection of related activities and deliverables. Work Streams are planning tools that provide work product context and cohesive touch points for the teams.

Each Work Stream is intended to result in one or more Milestone. A Milestone occurs when planned activities or deliverables conclude, accompanied by a valuable, functioning result that can be communicated externally to IDESG. Milestones are significant achievements towards realizing the Vision, and are likely to co-incide with Plenary meetings to simplify communications.

A Deliverable is a well-scoped, specific document or other output that is created by a working team led by an accountable individual. TFTM members create Deliverable Definitions using a simple lightweight template, to allow for coordination and tracking of work effort. At this time, TFTM does not intend to establish a formal approval process for Deliverable Definitions. The intent is to encourage members to self-select work that fits the TFTM goals, self-define the work and get working on the deliverable.

The Work Product Scheduling activity will determine how much, if any, overlap occurs between Work Streams.

Design Assumptions are used to maintain consistency in the design and elaboration of Work Streams, Milestones and Deliverable Definitions.


NOTE: The Work Plan and related schedules, plans, outlines and documents are DRAFT FOR DISCUSSION
until ratified by the TFTM Committee and, in some cases, the Plenary.


Work Plan Design Assumptions

In order to structure the work plan, several assumptions and work plan design choices are made:

  • Requirements should drive design
  • The NSTIC Four Principles will be fully represented in and integrated with the Requirements
  • Design factors include: design for early bootstrapping and incremental maturation and development, environmental change is inevitable so plan for change, design for evolution, embed agility in all work planning, design for growth, design for many contributors working towards common goals.
  • Work will be deliverable-based
  • Work will be organized into Work Streams to enable parallel work effort and distribution
  • Work will be scheduled enable realistic time sequencing and coordination
  • The Work Plan will be arranged to achieve quick onboarding of a small number of Trust Frameworks, Federations or ID Solutions. This approach is to quickly establish enough policy, requirements and processes to bootstrap a more robust and complete ecosystem.
  • Each Work Stream should use a similar approach: Gather Requirements; Consider Use cases; Determine Solution Options; Design Solution; Design processes; Implement
  • A lightweight project management process should be used for Work Streams: initiation, planning, execution, monitoring, closing

High Level Work Breakdown

Reminder:
There are three primary TFTM constructs:

  • The Identity Ecosystem (IDE) which is comprised of a range of Participants (organizations, individuals, service providers, certifiers, etc);
  • The Identity Ecosystem Framework (IDEF) which is used to govern the IDE; and,
  • The Trustmark Program which has processes for identifying and acknowledging IDE Participants, in conformance with the IDEF.

Simplified Work Streams

TFTM-WS1: Establish an Interim ID Ecosystem Framework, Interim ID Ecosystem & Interim Trustmark Program

  • Document the mandatory and optional high level requirements for Early Adopter Participants in the Interim ID Ecosystem
  • Design the Interim ID Ecosystem Framework required to support the Interim ID Ecosystem
  • Design the Interim Trustmark Program required to support on-boarding of candidate Early Adopter Participants of the Interim ID Ecosystem
  • Gather information about existing Trust Framework, Federations, ID Solutions
  • Design and Implement 'White Pages' directory service
  • Screen and qualify a small number of potential Early Adopter Participants
  • On-board the Qualified Early Adopter Participants using the Interim Trustmark Program

TFTM-WS2: Design the ID Ecosystem Framework and ID Ecosystem

  • Gather ID Ecosystem Requirements (business functions supported, participant characteristics, technology requirements, non-functional)
  • Gather requirements for ID Ecosystem Framework (governance, policy, standards, functions)
  • Design conceptual model and solution architecture for ID Ecosystem Framework and ID Ecosystem
  • Design services model and functional model of ID Ecosystem Framework

TFTM-WS3: Define a Trustmark Program

  • Gather Trustmark requirements
  • Gather Trustmark Program requirements
  • Design Trustmark Program Policy and Processes

TFTM-WS4: On-board ID Ecosystem Participants (Trust Frameworks, ID Federations, Credential Federations, ID Solutions)

  • Discover/Engage/Categorize potential Participants
  • Use the Trustmark Program to evaluate potential Participants and on-board as appropriate
  • Manage Participant status in the ID Ecosystem

TFTM-WS5: Facilitate or Establish interoperability between Participants (**NOTE** This assumes that participation in the ID Ecosystem and Participant Interoperability are distinct states)

  • Gather Interoperability Requirements
  • Define supported types of interoperability and their requirements (technical, business, legal)
  • Describe interoperability capabilities of ID Ecosystem Participants in a directory service

TFTM-WS6: Design ID Ecosystem Operations Processes and Structures

  • Gather requirements for ID Ecosystem Operations
  • Define and select an option for one or more organizations to operate the ID Ecosystem, based on the requirements

TFTM Committee Work Plan Management

This is TFTM Work Stream 0

The TFTM Committee Work Plan Management activities are concerned with planning the work of the committee itself, and include:

  • Lightweight Project Management Office functions, for example:
    • Coordination of Deliverable Definitions (including work effort estimates, publication, scope)
    • Schedule tracking
    • Publication of Deliverable drafts
  • Reporting outward/upward as required
  • Communication and coordination of TFTM Work Plan schedule with other Committees