Talk:Aaron log/XM Project Page Prototype 2
Contents
Explainer Video Script
OSE Goal
To become the most authentic and collaborative project in the world.
Essence of Project Page
To provide a single highly visible page that can provide ready access to all relevant project information - such as transparent access to all activity, process steps, accomplishments, and results on one page without leaving the page and without scrolling more than 2 pages down - while allowing for task addition on the task board without leaving the page - while allowing for updates of Status and Control panel to be done readily - with all display of relevant project information available from this single interface.
Put a True Fans Subscription
Tasks
3/31/11
- Team members - need to be shown clearly.
- Embed the simple platform instructional in first window
- In status box - is there a way to protect the verification of the Verified (so the doer does not fake verification by signing for verifier?)
Older
3 columns in log sheet - definition of done, done, and verified - Focus of definition of done is to do test driven developmentOn the Development Steps box, do 2 tabs - one is a blank page, and the other is the explanation of all the steps.To join team, email the scrum master. Add an email to on top.Aaron does a video screen capture for his first Vlog, and adds an Aaron update vlog box at the bottom. Don't be shy, we're creating culture.Add osebri.wordpress.com - feed to her videos on her blog- In the main vlog feed, see if we can do 4 choices: Scrum at FeF, Agriculture, Construction, and Prototyping
- True Fans - update number of True Fans - and put in a box at bottom.
- Do Dwolla as our new preferred method on True Fans -
Second Tier - 4 boxes below the Scrumy. 2 vlogs, 1 True Fans, and Greater Vision- Stats - Second Tier of the Second Tier - Do total hits on ose.org. number of views of main TED talk.
- for factor e farm Scrumy, do OSE_organization, fabrication, agriculture. And construction scrummies.
- Main vid feed is Daily Standup
- Secondary vid feed is entire FeF playlist - updated dynamically by many peeps at FeF. Quality control standards defined.
3/26/12
- For every sticky, we define definition done scrolling down on the sticky in Scrumy
- On Master Control Panel - we list steps, marcin add other + review steps, second column is definition of ready, definition of done, and link to further information.
Goals by 3/31
- General design: MAXIMIZE GRANULARITY TO ALLOW HIGH-LEVEL FEEDBACK TO HAPPEN WITH MINUMUM TIME EVERYWHERE POSSIBLE
- Complete the Development and Resources window - basically breakdown into as many steps as possible, and then fill in the standards for each page.
- Each step gets a general standard and procedure linked in the first column
- Includes definition of step, procedure, definition of ready and done, review procedure, acceptance procedure
- Each tool has the specific steps linked to in each
- Each step gets a general standard and procedure linked in the first column
- Get one Scrum Master and Product Owner for a particular step
- Prove Process for 1 tool
- General Requirement: 2 fabricators build 50 machines in 1 year, and 2 people maintain entire infrastructure for 200 person community
Budget
- $2k Scrum Master + $2k Product Owner (Calculation) per month
- 3 month cycle - $12k in project management
- for 20 projects scaling - $240k organization overhead
- Or - $80k/month for overhead
- Actual work - $2k - Design, $2k/prototype, $2k document, $2k CAD, $2k publishing (calculations and assessment and review assessment by Product Owner, review by Scrum Master)
- Pair up Best in World Mentors, Advisors, and SMEs with Low Cost (Competent but not Exceptional) - so that we pay $2k for design that would otherwise cost $15k or so.
- Or - $80k/month for overhe
Strategy
- We provide del-siloing services for SMEs
- Scrum Master develops Advisory Team and SME Team - goal of recruitment
- Rapid transfer of information from SME to Product Owner
- Product Owner organizes SME Flash Mobs
Goals by 4/7
- Executives recruit Scrum Master and Product Owner for each of 50 tools.
- For tools with multiple components, Scrum Master and Product Owner owns all of them - they do the entire machine
- Scrum Master recruits the working team
- Scrum Master and Product Owner come to Factor e Farm
- Documenter documents the development process, starting with explaining the Product Page
How To
One Project page handles all the components of a device. The additional components are simply listed as new spreadsheet pages on the Development and Resources Window
Recruiting Strategy
- Sprint -
- Marcin to pull in a - flash team - requires social capital
Granularity in taskboard
To provide fast high level feedback and basic structure while remaining agile
- Setup one taskboard per team (product or product group, FeF, org, ...)
- For each product: (At least one) story for each of the 73 steps on the master list, starting with its number), example taskboard
- Additional stories should start with one of the step's number as well to provide context.
- Get Scrumy pro ($5/month) to get live updates from Taskboards (Kind of feed of every action (create/edit/delete) on every task/story/sprint) using Webhooks
- Start with a Definition of Done for each step on the master list, not one per story. Acceptance criteria should be defined per story (task).