Example 1: A Software Project
Expedition Brief
Make a system for designing productivity forms using Javascript+HTML5+NodeJS capable of generating PDF files for download
context
Sri Software Ascendancy
motivation
Producing semi-custom forms like the ETP Journal and Word Counting Calendar are slow and cumbersome, but they are good products. Developing this system could open Print-On-Demand workflow to my printing company, and would establish some credibility+uniqueness in the productivity design sapce.
expectation
Increased ability to provide custom services very quickly; increased ability to produce unique interactive experiences; increased skill in javascript webapp development
waypoint 1
minimum drawing prototype - (1) reproduce existing form elements in canvas (2) simple POC webapp using canvas (3) define data description language for POC
waypoint 2
minimum data definition - modify POC webapp to use data description language from expedition 1
waypoint 3
minimum PDF generation - (1) equivalent PDF drawing for canvas instructions (2) simple POC server-side app to draw PDF file (3) use data description language to drive server-side POC
collectables
proof-of-concept code to develop into a new form offering on dsriseah.com; webapp UI library; server PDF library; form description language parser
Expedition Launch and Members
The expedition is recruiting members, after which a launch date will be set.
- Sri - Expedition Initiator
PRE-EXPEDITION PREPARATIONS
[ ] Make a printer-friendly 4x6 card framework
[ ] Use 4x6 framework for current expedition list and ghdr goals
Example 2: A Working Group Expedition
Expedition Brief
Metareview of Essential Systems for Personal Knowledge Management to produce a working group that motivates our individual works.
context
We are all interested in making PKMS. How do we systematically define the features we use? What are the organizational and operational principles?
motivation
It's hard to motivate myself to work on my PKMS in a vacuum. I would like to talk about the subject in detail and create concepts that we can all share and optionally implement in our own way, individually or in collaboration.
expectation
Data structures, terminology, process ideas, impromptu collaboration. The goal is to create shared ideas that we can individually "riff" on.
waypoint 1
A gathering offline, discussing in Expedition HQ forum. until something specifically actionable catches someone's interest.
waypoint 2
A virtual gathering, in Expedition HQ video chat, to pick some initial things to work on. Or support, if someone has an idea.
waypoint 3
?
collectables
Participants come away with ideas, code, or experiences that have sharpened their understanding of PKMS needs. Perhaps working tools and code have resulted. An initial way to manage a group of this type.
Expedition Launch and Members
- Sri - Expedition Initiator
PRE-EXPEDITION PREPARATIONS
[ ] Find peeps who want to advance their practical knowledge
[ ] List expectations, keep bar low, require participation
[ ] Call for meeting