Pt. 5: Purchase Goods and Services.

Pt. 5. Purchase Goods and Services.

Our basic requirements have been set out, and basic design initiated. Additionally a contractor has been selected in the way of an associate.

Our next stage is to aquire their services, to which end the associate was contacted, and invited to initial meetings.  Contractor resources were discussed as well as initial ideas for the project, and creative amendments were made.  It should be reiterated at this time that the selected associate specialises in this particular field of study themselves, and is familiar with the material taught on this course; so further input was discussed.

Initially the suggestion was that the analysis and design team script the material themselves, with the associate bought in to the 'organisation' as staff augmentation. However, as the meeting progressed it became clear that a total outsourcing approach would suit the project needs far better.  

In this context it was agreed that our contractor would design and implement (record) the system fully.  Given the initial spec, and creative discussion of the meeting, the associate would generate scripts, modify (after feedback) and record the dialogue.  This would not only ease time pressures on the analysis team, who have other material to generate, but also give a good measure of experience in creating teaching materials to the associate. 

Development approach

As development approaches are themselves part of the core teaching on this course, a simple agile methodology was selected (RAD).  Other agile methodologies that are discussed in the course (rapid prototyping) were deemed to be a bad fit for this project due to the nate of the product.  

Creative Discussion

During the initial contractor briefing the requirement were laid out, and contractor resources were discussed (which impressions were in their repetoire).  The following amendments were made.

The six requirements were split into two catagories, the first, on development of systems, the second on project management.

Development meterials to be created using impressions of Muppets, in a cookie factory scenario.  

1. System type case studies: Four distinct voices for different system types. The Count for Accounting systems etc.  
2. Rich-pictures: The Cookie monster (factory foreman) describing the process within the system.
3. Entity Relationships: Kermit the Frog detailing information passing around the system.
4. Development type case studies: Mixed muppets discussing issues.

Project Management meterials to use popular film characters.

1. Good-plan/Bad-plan: Bad plan script taken from 'Jingle all the way' film using an Arnie impression. Good plan as Golum in the LOTR series. Middle plan as Korg from the Avengers francise.
2. Use-case studies: Full plot of Avengers infinity-war/endgame from Korg's perspective.

Handover to Outsource Contractor

With these requirements in mind, the development details were handed over to the contractor, and fees paid.  The product is still in development at this time.