[163] in Project_DB

home help back first fref pref prev next nref lref last post

An alternative proposal for V2 and V3...

daemon@ATHENA.MIT.EDU (Tim McGovern)
Wed Jul 9 12:34:41 1997

Date: Wed, 9 Jul 1997 12:31:26 -0400
To: project-db@MIT.EDU
From: Tim McGovern <tjm@MIT.EDU>

<bold>It seems to me...</bold>


We have a wonderful opportunity over the next three- to six-months in
the Project DB "service" efforts.  As of today, we have a working
service, the interface is usable, although occasionally misleading, or
non-intuitive, and both the UI and the data schema are somewhat hard to
change.   


Last week, I heard that our <bold>goals</bold> for the future were:


	1) capturing, and/or sustaining, Director interest & participation

	2) expanding the use of the service by team leaders, and perhaps by

           team members, and 

        3) seeking ways to encourage (and provide support for) projects
to

           incorporate the service into everyday work.


I propose we plan two releases over the next six months or so, Version
2 and Version 3, rather than just a single momentous one as we
discussed on July 3.  


Here's how I see these two releases shaping up.


<bold>Version 2</bold>


The highlight of V2 would be the new-and-improved UI based on BRL,
<bold>without</bold> any changes to the V1 data schema.  This takes
advantage of work already well along, and positions us well for Version
3.  


A high-level workplan for V2:


	* make any changes that we need to the BRL UI (based on current

          testing), 

        * document the system more fully, 

        * advertize the system via Quick Start-type sessions, 

        * hold a TNSTAAFL perhaps, and so forth.  


     [Details of the "non-code" parts of the V2 project need some  

      further discussion.]


V2 is a quick win in support of Goals #1 and #2, and will sustain all
of our stakeholders, and engage them in thinking about V3.   I think
the BRL UI will be very well received.  BRL also gives us a chance to
make smaller incremental changes in the UI should we decide they are
critical to support any of our Goals.  I propose we shoot to make V2
public on or before October 1, 1997.


<bold>Version 3</bold>


The highlight of V3 would then be the revision of the data schema, the
UI, and associated facilities, to support the requirements that we can
begin gathering this summer.  With broader participation of V1 and then
of V2 over the next few months, we can fine-tune the requirements much
better than we ever did for V1.  I propose we shoot to make V3 public
on or before January 1, 1998.


Let me know what you think...anything requiring more explanation?


Thanks,

Tim





home help back first fref pref prev next nref lref last post