macauley@shiitake.UUCP (07/14/89)
Development Methodology Meeting 6/9/89 by J. Spencer, R. Bailey, G. Grossman
Doc Bailey (Status of HP meeting on 6/8/89)
Greg Micheals (HP Strategic Business Manager) is very pleased with the
dedicated effort of Addamax on the HP/B1st Project.
Peter Fenton (HP Systems Specialist) will notify Addamax on future travel
plans for HP Engineers to the UK.
Gary Grossmann (Discussion on "Lessons Learned, Mistakes that Surfaced and
Suggestions Offered from our Progress w/ All Passed Business")
1.) All involved with the HP Integration have done a
great job and managed to stay under budget!!!
2.) Problem: We have committed ourselves to a very complicated
project. "Networking"?
We need to reintroduce ideas on thoughts on commitment to quality of the
product, delivering a functional port, and then cleaning and implementing]
the finishing touches after the functional port.
THINK ABOUT WHAT THE CUSTOMER WANTS!!!
What can Addamax learn from our negotiations and development up to this
point?
We failed at giving the customer a demo. We need to give our future customers
a demo in order for them to have a taste of what ADDAMAX has to offer!!
What else is missing in Product Development? This is what this meeting is about!WE NEED YOUR INPUT AND IDEAS TO IMPROVE OUR STRATEGY!
G.G. (A display of a matrix for deliverables was placed on the board)
Demo(Prototype)| Alpha | Beta | Version (1.0,1.1...2.0)
____________________________________________________________________________
Purpose | | |
___________________________________________________________________________
Characteristics | | |
____________________________________________________________________________
Reviewed | | |
____________________________________________________________________________
Tested | | |
____________________________________________________________________________
Completed | | |
___________________________________________________________________________
Frozen | | |
____________________________________________________________________________
Components | | |
____________________________________________________________________________
Security Requirements | | |
____________________________________________________________________________
Functional Specifications | | |
___________________________________________________________________________
Design Specifications | | |
_____________________________________________________________________________
Code | | |
______________________________________________________________________________
Test Specifications | | |
_____________________________________________________________________________
Tests | | |
_____________________________________________________________________________
Functions | | |
_____________________________________________________________________________
O.K. Here is the chart, now we need specifically define each stage then ask
the customer which of the parts are needed for their integration.
This system can only work if every one of us can give their ideas and
definitions on an on going basis. This project will always be in work!!
All thoughts, suggestions, definitions, brainstorms, that cross your
inquisitive minds should be jotted down, stored in black and white and
communitcated through out Addamax. The results of group effort for our
company have already produced a great TEAM, Lets produce the #1 B1st Product!!
IDEAS and SUGGESTIONS:(PLEASE ADD TO THE LIST, Just hit w and add a note
to this file)
1.) Check w/ Dorothy and see if and when feedback comes in from the vendors
comments on the B1st Kit. Funnel this information, past the maintenance
team to development in order to fix and learn from this crucial information.
2.) Addamax is going to look into distributing our B1st Kit in agencies such
as CIA, Applied Physics Lab, etc.. in order for Addamax B1st to first
of all get recognition, and secondly to test our system.
3.) Marketing Ideas: Addamax needs to immediatly begin giving version numbers
to the kits we are distributing to customers and to potential customers,
We need to have the standards committee meet on this ASAP.
4.) The technical end needs to get all the feedback available from our
customers in order to use this information during future development.
5.) In office suggestion: (technical department) directed to the standards
committee: When things become a standard the new standard needs to
be included in a standards document. MAIL SHOULD BE SENT OUT WHEN ANY
STANDARDS CHANGE .