Page tree

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Individual cards may have different members, checklists, comments, due dates, attachments, as defined in trello by the board and procedure owners:



Work Sequence

Image Added

Image Added

Image Added

Image Added

Image Added

Image Added


The following table defines the steps, from start-to-finsih, for new deliverables.

StepPhaseDocumentation Type
Process

DefineOperational Baseline

1
Proposed
  1. Create a new deliverable board in Trello.
  2. Set the background.
  3. Make the board team visible, and add team members.
  4. Create 4 lists: "Proposed", "Documented", "Validated", "Communicated".
  5. Add cards in the “Proposed” section describing the different aspects of the deliverable.
  6. Create a card on the Masterplan board, with the name of the new deliverable board.
  7. Add the “Label” according to the Openvino Silo.
2
Documented
  1. Edit the description of each card, with information about the deliverable procedure. Include checklists, due dates, and any relevant attachments.
  2. Move the procedure to the “Documented” column.
3
Validated

Have you received feedback (thumbs up) from all deliverable team members indicating all is good to go?

Once you have, move the card to the “Validated” list.

4
Communicated
  1. Post a short blog entry on the wiki, including a brief description, and tagging team members involved. “On Thursday, we begin working on the Vineyard IoT sensor data to Sidechain project”.
  2. Move the card to the Communicated list.
5


  1. Once ALL the cards are in the Communicated list, move the cards back to the Proposed list
  2. Move the Masterplan card to the “Requirements Definition” list.

MeasureRequirements Definition

6
Proposed
  1. Create the template in the wiki where these deliverable procedures will be documented, and communicate to the team. At this stage both the “Requirements Definition” template, and the “Test Plan” template should be created.
  2. Assign responsibilites to team members.
7
Documented
  1. Have team members fill in the “Requirements Definition template AND “Test Plan” template, creating and assigning individual CTQ (critical-to-quality) entries for every functional and systemic requirement.
  2. Move the card to the Documented list.
8
Validated

Have you received feedback (thumbs up) from all deliverable team members indicating all is good to go?

Once you have, move the card to the “Validated” list.

9
Communicated
When a card has been validated by all team members, send a short message to team members informing that this card is closed, and move it to the “Communicated list”.
10


  1. Once ALL the cards are in the Communicated list, move the cards back to the Proposed list.
  2. Move the Masterplan card to the “Architecture Specifications” list.

AnalyzeArchitecture Specifications

11
Proposed
Create the template in the wiki where the Architecture components (hardware, software, networking, identities, etc.) for the deliverable procedures will be documented, and communicate to the team. Assign responsibilites to team members.
12
Documented
Team members create the necessary documentation of servers, operating systems, applications, network configurations, directory services, etc. that underpin the deliverable. Move the card to the Documented list.
13
Validated
Have you received feedback (thumbs up) from all deliverable team members indicating all is good to go? Once you have, move the card to the “Validated” list.
14
Communicated
When a card has been validated by all team members, send a short message to team members informing that this card is closed, and move it to the “Communicated list”.
15


Once ALL the cards are in the Communicated list, move the cards back to the Proposed list, and move the Masterplan card to the “Implementation Plan” list.

DesignImplementation Plan

16
Proposed
Create the template in the wiki where the “Implementation Plan” for the deliverable procedures will be documented, and communicate to the team. Assign responsibilites to team members.
17
Documented
Team members implement AND document the necessary components for the procedure. THIS IS WHERE THE ACTUAL WORK GETS DONE. When work AND documentation is complete, move the card to the Documented list.
18
Validated
Have you received feedback (thumbs up) from all deliverable team members indicating all is good to go? Once you have, move the card to the “Validated” list.
19
Communicated
When a card has been validated by all team members, send a short message to team members informing that this card is closed, and move it to the “Communicated list”.
20


Once ALL the cards are in the Communicated list, move the cards back to the Proposed list, and move the Masterplan card to the “Test Plan” list.

VerifyTest Plan

21
Proposed
Review the Test Plan created in step 6. Assign testing responsibilities to team members.
22
Documented
Execute the test plan, and make any necessary updates or changes.. When this is complete, move the card to the “Documented” list.
23
Validated
Have you received feedback (thumbs up) from all deliverable team members indicating all is good to go? Once you have, move the card to the “Validated” list.
24
Communicated
When a card has been validated by all team members, create a short message to the team, entry indicating that the testing phase has finished successfully.
25


Once ALL the cards are in the Communicated list, move the cards back to the Proposed list, and move the Masterplan card to the “Test Plan” list.

ControlControl Plan

26
Proposed
Create the template in the wiki where the “Control Plan” for the deliverable procedures will be documented, and communicate to the team. Assign responsibilites to team members.
27
Documented
Team members create the necessary documentation for operating the deliverable service, including daily, weekly, monthly, and periodic mantenance tasks. This should also include monitoring variables and thresholds, and security constraints. Once this is finished, move the card to the “Documented” list.
28
Validated
Have you received feedback (thumbs up) from all deliverable team members indicating all is good to go? Once you have, move the card to the “Validated” list.
29
Communicated
When a card has been validated by all team members, create a short BLOG entry indicating that the deliverable has gone into production. Congratulations! You have finished.
30


The board entry can be archived.

Team Coordination

What are our communication tools for our extended team: Telegram group: OpenVino and Whatsapp group: OpenVino Video.

When and how are project meetings held?

Risk Management

What risks have we identified that might derail our efforts to reach our success criteria, and how we are mitigating these risks?

Change Management

How can we implement changes into the project plan in mid-stream?

Timeline

How is the project implementation plan projected on a timeline, and what are the key milestones?