PART ONE: Resume

In preparation for the formation of the teams, each person should create a "resume", which prioritizes their interest in fulfilling the different development/team roles, as well as their education and "work" experience which justifies why they are a good match for the role(s) they hope to fulfill. (Note: "No experience" and "lots of experience" could be equally justifiable reasons for assuming a role.)

The team roles are:

• Project Manager
• Requirements Engineering (external specification)
• System architect
• Programmer
• Quality Assurance (Verification & Validation, testing)
• User Documentation
• Configuration Management.

Once formed, the teams will have flexibility/input in the division of labor--this will primarily be used to aid in the team formation stage.

NOTE: This was partially a test (as these will always be). Only one person asked what format the resume should be in. Very similar to the example given in class where the QA group grabs the CD without asking how it's supposed to work.

• BEST HABIT (similar to the idea of Best Practices, which will be covered in the future): The point of the request/transaction is one of the best opportunities to gather the info ("requirements spec.") on what the "deliverable" should be.
• (The answer, by the way, is "paper or email". If you send it electronically, just send ASCII text).

PART TWO: Process Model

PART ONE: Resume

As in version 1.0, above.

PART TWO: Process Model (revised)

The format should be:

• Title/label for Process (e.g., "Cook-like-hell", or "Waterfall morning prepardness");
• Concept/Summary of the outcome of the process (e.g., "Spagetti dinner" or "Outta bed and ready for work/school");
• Process
  • Tools
  • Methods/Techniques
  • Practices/Standards
  • Activities
  • Ingredients/Building blocks
  • Life-cycle (Sequence of events/activities)

NOTE: Feel free to keep it at a fairly high level of abstraction. If you want to go into detail, please make sure that the presentation of the details doesn't prevent the user from being able to get the 'big picture'.