Difference between revisions of "Blueprint-tech-agenda"

From IVP Wiki
(New page: ==A. Information Valet Service mission 11 a.m. -11:30 a.m.== *Confirm mission and any supporting objectives **See: http://informationvalet.wordpress.com/about/ **Also: http://www.mediag...)
 
 
(One intermediate revision by the same user not shown)
Line 1: Line 1:
 
==A. Information Valet Service mission  11 a.m. -11:30 a.m.==  
 
==A. Information Valet Service mission  11 a.m. -11:30 a.m.==  
 +
*Confirm/revise today's agenda/schedule
 
*Confirm mission and any supporting objectives  
 
*Confirm mission and any supporting objectives  
 
**See: http://informationvalet.wordpress.com/about/
 
**See: http://informationvalet.wordpress.com/about/
Line 33: Line 34:
 
==H. Next steps==
 
==H. Next steps==
 
*Confirm next steps.
 
*Confirm next steps.
 +
 +
==Jeff's observation==
 +
 +
Jeff VanderClute observes in email:<br>
 +
This can probably just be stated verbally, but I'd like the group to
 +
give itself permission to view Information Valet as a multiphase
 +
evolution, so that we're not trying to solve too many problems
 +
simultaneously.

Latest revision as of 17:01, 31 December 2008

A. Information Valet Service mission 11 a.m. -11:30 a.m.

B. Ownership, control structure -- 11:30 a.m.-11:45 a.m.

  • Densmore outlines proposed corporate structure

C. Potential role of The Associated Press -- 11:45 a.m.-noon

  • Randy Picht will use WebEx to present features of AP Exchange

D. Elements of the service -- noon-1 p.m.

  • What problem(s) are we going to solve?
  • Who are our target partners/customers?
  • Discuss and reach consensus on the service features
  • What are the relationships supported/enabled?
  • What are the values exchanged?
  • What are similar existing services?

E. Lunch (in the hotel restaurant -- half the cost of catering)

  • Continue discussing features/relationships to be supported

F. The nuts and bolts -- 1 p.m. - 3 p.m.

  • Diagram / agree on the relationships
  • Be explicit about things InfoValet will **not** do (eg: determine pricing/bundling)
  • Identify the necessary technologies, partners
  • Define the relationships among them
  • Determine what's off the shelf, or what needs to be built in terms of interfaces or missing pieces.

G. Documentation - 3 p.m.-3:45 p.m.

  • Document our proposal sufficiently for Steve Mott/Bill Densmore to incorporate into the InfoValet Project development plan.

H. Next steps

  • Confirm next steps.

Jeff's observation

Jeff VanderClute observes in email:
This can probably just be stated verbally, but I'd like the group to give itself permission to view Information Valet as a multiphase evolution, so that we're not trying to solve too many problems simultaneously.