DataPortability Hack of the Month Club
Project Objective
To:
- promote a series of DIY technology projects supporting data portability today
In a way that:
- Requires minimal effort, perhaps less than one person day to implement
- Produces immediate benefit for the implementer
- Introduces a best practice without overwhelming budgets or staff
- DataPortability.dev supports with a prepared mini-cluster of wiki/mailing list/irc for supporting the developer
- DataPortability.ev supports with a prepared mini-business case
- Lists and acknowledges participants
So that:
- DataPortability.org promotes existing technologies (fulfilling its mission)
- DataPortability.org demonstrates technology leadership
- DataPortability.org makes the point that dp need not be a big bang or boil-the-ocean effort
- DataPortability.org attracts technologists and developers into its community
About this project
Contributors to this page:
Brady Brim-DeForest, Elias Bizannes, Phil Wolff
|
Project Scope
What are the project's borders?
- What is specifically in and out of scope?
What are the project interfaces?
- What other projects are affected?
What are the critical requirements?
- If you do nothing else, what is the essential core of the project?
What are the project deliverables?
- What work products will you leave behind?
What are the project's metrics?
- Measures of completeness?
- Measures of quality?
- Measures of effort?
- Measures of created value?
Current Issues
- Briefly describe any issues that will need to be addressed prior to or during the project
Before you start...
Pleasure and Business Cases
Why do this project?
What happens if we don't do it?
Why do it now?
How critical will the impact of the project be?
How does this project support our overall mission?
Which stakeholders will enjoy the project benefits?
Risks
- What could go wrong? (both systems-related and user-related)
Countermeasures
Costs
- List all hardware, software, network, staff, facilities and other costs
|
