Tripharn Teki, Nick Small, Shawn Boughey, Karolina Latkoska PG Project Maniacs SPQM / SEP

Tripharn Teki, Nick Small, Shawn Boughey, Karolina Latkoska Themes from Week 1 Get to know your project. Determine what you need to know. Meet your project team.

Tripharn Teki, Nick Small, Shawn Boughey, Karolina Latkoska Week 2 What is your project? –GazCar ECS (electronic communication system) 2.0 What are you planning? –Re-design of data store Data Migration Communication system between shop fronts –External communication system with customers –DSS for customers –Online booking system for customers

Tripharn Teki, Nick Small, Shawn Boughey, Karolina Latkoska Week 2 When will your project be completed? –TBC Where are you up to now? –Initiating. (Business Analysis / Project Viability study) What are the issues and problems? –Discussed further in a few slides. What are you doing about them? –Discussing with client.

Tripharn Teki, Nick Small, Shawn Boughey, Karolina Latkoska Stated requirements GAZCar have a customer database (written by the founding director’s son) that stored all of the conversions for each car, the customers name and contact details, tank inspection dates and warrantee information. It has been written in ACCESS and appears to be quite fragile when accessed by all 30 centres at once. The field naming is haphazard and allows operators to enter data in free text fields making the data hard to sort and search effectively. (Redesign) Each booking accepted by each conversion workshop is to be recorded locally and replicated to the head office as a transaction file. (Distributed Application) GAZCar would like to see their conversions promoted perhaps with a decision support system to help potential customers make a choice about the conversion they might best select. (DSS – online?) A system that allows customers to make a booking would be useful. Customers might make a booking for a new conversion (at one of the several stages), a stage upgrade, a tank inspection or fitment of one of the options. (Online booking)

Tripharn Teki, Nick Small, Shawn Boughey, Karolina Latkoska Client follow up questions Client Time ? Cost ? Scope ? –How much do we have? Is it fixed? Database –Data migration What data is already held? How is the data stored in the Access DB? –Transaction file. Time constraints?

Tripharn Teki, Nick Small, Shawn Boughey, Karolina Latkoska Client follow up questions Customers Expected customer load –How many concurrent users expected? DSS through a website or in store or both? –Has a domain been registered? Bookings –What information is required from customer? –Does the customer get confirmation of booking, or just request a booking?

Tripharn Teki, Nick Small, Shawn Boughey, Karolina Latkoska PGPM’s SWOT Objective – Complete the project to a very high standard. Strengths –Post Grad students with > 40yrs combined experience in PM or Soft Eng. –We’ve all worked together, to some degree, in other subjects. Weaknesses –? Opportunities –Good networks within our own employment areas to leverage experience or advice from. Threats –All FT employees with work / other commitments, which are likely to be higher priority.

Tripharn Teki, Nick Small, Shawn Boughey, Karolina Latkoska PGPM’s Communication How:- The majority of the group communication will be done through a free online Wiki (wikispaces.com) Alerts are setup for when changes are made so that others in the team can confirm. History is tracked and also has a simple system. Each person in the team is allocated a role. Each role contains tasks for which they are responsible for completing. These are outlined each week in the tutorial. Why:- Central store for information. Maintains history. Accessible from any web enabled computer. When:- Weekly meetings after tutorial. Activity Diagram for Communication using documents is available on the Wiki

Tripharn Teki, Nick Small, Shawn Boughey, Karolina Latkoska Work Breakdown Structure On the wiki