OSE Meeting: OSE Development Method Planning
Owned by: Operations Manager
POC for collaboration: ops@opensourceecology.org
V.08-12-13
Formally known as:
Development Process and System Implementation Plan
July 26, 2013
Using the below process to implement product development
Current State Map
Stakeholders* - no particular order
- OSE Executive Staff
- Tech Collaborators - Subject Matter Experts
- DPVs
- Product Users
- Foundation
- True Fans
- Financial Contributors
- Supply Chain
- Transportation / Logistics
- “Open Source” Advocates - not a product user
- Community
- Executive Director
*As the steps in the process develop, need to consider the stakeholder and how they integrate
Purpose of mapping current state, per TCM -1) Clearly show progress and elimination of waste/increase in efficiency and a higher level of thoroughness/quality to the board/foundation
2) ID problems of current state despite complexity
4 Current States:
Wrap up
Planning Products/Tools Created:
Planning Facilitator (TCM), next steps:
1) Review current state for completeness
2) Complete a matrix (TCM prepping for July 29) that IDs each step in the current state and assesses:
3) Analyze Current State for gaps, missing triggers, issues, risks, lack of products/instructions, lack of resources, multiple re-works, lack of comm channels,etc.
4) Map out our future state as correct the issues of the current state
July 29, 2013
DPAI Current State July 2013 Matrix
Future State Map
Continue too:
a) clarification/direction
b) provide a vector check
Development Process and Implementation Plan
DPAI Current State July 2013 Matrix
July 30, 2013
Goal: Complete mapping Future State July 2013
Week Agenda:
July 28 - Current State Mapping
July 29 - Complete Current State Mapping and Matrix
July 30 - Completing Current State Matrix then Future State Mapping
July 31 - Build a Development Process based on Future State
Aug 1 - Create Future State Matrix, which will include deliverables for Development Template: Protocols & Example Work Product - resulting in a tangible developmental timeline
Aug 2 - Input into PM & Resource Load
July 31, 2013
Day Agenda:
CREATE IDEAL FUTURE STATE
1) We list assumptions (i.e. things we cannot change, such as products that make up the 50 GVCS)
2) We map out each step and ID supporting documentation/deliverable, communication method, and trigger.
3) If someone wants to add a step, deliverable, etc; and there is disagreement, we flag it and move on--unless it will largely impact other steps.
4) The future state we should focus on is the DPV and Remote Collaborator future state, as it will be easy to adjust that current state to cut out RCs. I'm updating the Current State #2 matrix to match the steps we just went over for Current State #1.
5) For areas where we disagree and it can't be worked out in a short time (no longer than 10 minutes, I would say), we will ask the disagreeing sides to write up a pro/con list for each position. This may sound time consuming, but a) it will help us document the reasons for the decision, b) it will make people truly consider how important their sticking point is because it will require the to do more work, c) it will keep people off their soapbox.
EVALUATE IDEAL FUTURE STATE
Once we build Ideal Future State, we need to evaluate it for both roadblocks and assess it to ensure it addresses the issues/risks as outlined in the current state.
FUTURE STATE
Then we modify our Ideal Future State by removing roadblocks or building work arounds which gives us our Future State.
DELIVERABLES/TRIGGERS/COMM CHANNELS REVIEW
Then we review the deliverables, triggers and comm channels for each step. This will take some time. At this stage, let's start IDing what content should be included in each deliverable...for instance, for the deliverable "Specifications" the content we should ID should include: size, weight, power, transport method, functional specs such as load bearing capacity, speed, etc... Even though not all products have a "speed" option--we should be able to create a template that has the 80% solution where there is a section of the template that includes product specific functional requirements.
DELIVERABLE TEMPLATE CREATION
I recommend we divide up the deliverables and begin building templates or showing examples. Some deliverables may include an instructional (a communication channel)...these are just as important as templates and need to be created this week, even if they aren't great.
Assumptions
August 1, 2013
Ongoing creation of Future State July 2013
Participants
August 2, 2013
Ongoing creation of Future State July 2013
Participants
August 5, 2013
Create Ideal Future State July 2013 Matrix
TCM’s Agenda: Monday’s Plan - Ideal Future State
1) ID persons performing functions in the design/build phase of the ideal state.
2) Review / verify ideal state from beginning to end -- bump ideal state to current state to ensure we have removed "process" roadblocks,"
3) ID additional issues / risks -- this is where we ID resource constraints. We will begin completing the matrix for the Ideal State focusing
1) assign responsibility/authority
2) actions for that step (outline the actions)
3) ID products created (typically derived from actions
4) ID comm channels and triggers
5) ID step for issues/risks.
Note: Complete this, then ENSURE TCM, PL, DM buy-in prior to Future State development.
If entire OSE ES not available then > ID the "low hanging fruit" here and begin building templates
Future State Creation
1) Review Ideal State roadblocks, risks and issues and start removing the roadblocks, addressing issues, & burning down risks...
2) Create our Future State -- a deviated version of our Ideal State
3) Complete the matrix to include the modified future state
August 6, 2013
On Hold - PL/TCM out of the office
August 7, 2013
Ongoing creation of Future State July 2013
Operations Manager Note:
1) PL out of the office - Development Process is being reworked by DPV to fit current needs for LifeTrac 6
2) Upon PL’s returns, will pick up process
August 13, 2013
On Hold
August 14, 2013
Ongoing creation of Future State July 2013
1) Finish Ideal Future State Issues and Risks
August 15, 2013
Completed creation of Future State July 2013
August 20, 2013
Currently working to complete Future State August 2013
2) Working Future State
3) Taking Future State, build a Master Product Development Template in PM (just like what we did with LifeTrac 6 last week) and update the Master Product Development Board