1. (Winter 2016) Instructor: Craig Duckett
Lecture 04: Thursday, January 14th
FTP to BIT276 Team Site on Cascadia
PHASE 1: Discover WALK-THROUGH Teamwork

2. PHASE 1: DISCOVERY DUE: Tuesday, February 2nd, uploaded to Team Web Site and ZIPPED and uploaded to StudentTracker by Phase 1 Project Manager
Projects and Team have been selected!
Phase 2: Design due Tuesday, February 16th
Monday, January 18th NO CLASSES Martin Luther King Day
Tuesday, January 19th NO CLASSES Non-Instructional Day
Thursday, January 21st NO LECTURE: Instructor on MATH Hiring Committee
Tuesday, February 2nd NO LECTURE: Instructor on MATH Hiring Committee

3. The Team Project Five Phase Due Dates
One (1) Team Project for a Client (3-to-4 Members on Team) 1000 points Total
Phase 1: Discovery (200 Points) DUE TUESDAY, FEBRUARY 2nd
Phase 2: Design (200 Points) DUE TUESDAY, FEBRUARY 16th
Phase 3: Develop (200 Points) DUE TUESDAY, MARCH 1st
Phase 4: Distribute (200 Points) DUE THURSDAY, MARCH 10th
Phase 5: Documentation (200 Points) DUE THURSDAY, MARCH 17th (Last Day of Class)

4. I need to confirm… Carol’s Cascadia Username
Nguyen’s Cascadia Username

5. Setting Up Your Team Environment [ Step-by-Step ]

6. TEAMS Online Team Collaboration Programs (Free)
 RECOMMENDED

7. Phase 1 Discovery
A Closer Walk-Through

8. Phase 1 – Discovery A. ORGANIZE YOUR TEAM
OVERVIEW: Gather project information from your client to create a mission statement, mission objectives and site goals, and the data model that will provide information from the data. Based on your research and conversation(s) with the client, create a Strategic Brief document. Send a copy to the client and follow-up to confirm the completeness and accuracy of this scope document.
A. ORGANIZE YOUR TEAM
Get to know your team members by compiling a contact sheet with information from each member including an address and a brief bio. Decide on a name for your team. Choose project roles for each phase of the design. Record this on the team info sheet.
In order to facilitate the coordination of the team effort, each member of the team will act as a team-lead during a different phase of the project. As a group, decide who will act as team-lead during each phase. Choose a different team lead for each phase. For groups of four or more, your team may assign a co-lead role to two of the members.
Discuss and decide on a process that your team will use to divide up the team tasks and report out to the team on your individual progress. You will have some regular team meeting time in class throughout the quarter.

9. Phase 1 – Discovery

10. Phase 1 – Discovery B. MEET WITH YOUR CLIENT
Schedule a meeting with your team’s client between now and next week to discuss the database design. At least two members of your team need to attend the meeting. One team member should facilitate the meeting and one member should take notes at the meeting. a synopsis of the notes to the entire team and the client. Copy me on all exchanges with the client.
Before meeting with the client, develop a set of initial and follow-up questions to ask the client – send these questions to the client before the meeting and include your questions along with the client answers in your meeting notes. Be sure to request from the client all documents, forms, sample data, business rules, or comparable database examples that they can provide to help you understand their needs.
Develop a Strategic Brief document (see example below in Part F) to begin your data modeling process. You’re your conversation with the client, draft a mission statement and set of objectives for the database project. Determine the informational questions, decisions, data processes, and potential subjects, characteristics, and relationships for your data model.

11. Phase 1 – Discovery C. DEFINE YOUR PROJECT IN A STRATEGIC BRIEF
Create/Refine a database Mission Statement and Objectives
Creating a mission statement and a set of objectives will help to keep your data model focused on the core purpose of the project and the information that is needed to accomplish the purpose. The mission statement describes the purpose of the database project in the broadest terms. It answers the questions:
What is the project going to do?
Who is the project going to reach?
How is the project going to do it?
Why is the project needed?
The mission statement should be no more than three or four sentences.
Determine Objectives and Users:
Create a master list of objectives, ranked by priority for your Strategic Brief. Objectives are results; they are specific, attainable and measurable. Some possible questions to ask the client to help determine the web application objectives are:
What is the purpose of the database for the business or organization?
What are the short and long-term goals for the project?
Who uses the database information? What different types of users are there?
Why do people need this project?
Client Review
Review the Strategic Brief with the client via an exchange to confirm your understandings. Make adjustments as necessary based on the client’s feedback. Repeat this process until both you and the client are satisfied that the project is well-defined.

12. Phase 1 – Discovery D. DEVELOP THE DRAFT DATA MODEL
A clear understanding of the information needs and data processes will help ensure the completeness and effectiveness of the data design. Review the notes from the client meeting and supporting material to make a set of informational questions that describe information important to the project mission. List decisions, data processes, potential subjects, and their characteristics that seem to be important to the project mission and outcomes. This data model will form the basis of your database design.
E. FINAL SUBMISSIONS FOR DISCOVERY (DUE TUESDAY, FEBRUARY 2nd )
The team agreement that includes a team name, ground rules, and goals for the team, along with contact information, roles, and bios for each team member.
The typed synopsis of notes from the initial client meeting including the questions you asked, the client’s response and follow-up confirmation with client.
The supporting material provided by the client to help define the database project.
A set of categorized questions and decisions that outline the information that the client intends to draw from the database.
A Strategic Brief which includes the project mission statement, a set of objectives, and database users, the data processes, subjects, and their characteristics.
THIS WILL CONSTITUTE THE DELIVERABLES SUBMITTED FOR PROJECT_01 IN STUDENT TRACKER
It only has to be zipped and submitted once (preferably by the PHASE 1 LEAD or TEAM LEADER) 200 POINTS
ALL TEAM DOCUMENTS SHOULD ALSO BE UPLOADED SEPARATELY TO THE TEAM SECTION IN CASCADIA STUDENT WEBSITE

13. F: Example of a Strategic Brief

14. Interview Guidelines Participant Guidelines
Make the participants aware of your intentions.
Let the participants know that you appreciate their taking part in the interview and that their responses to the interview questions are valuable to the overall design project.
Make sure everyone understands that you are the official arbitrator if and when a dispute arises.
Interviewer Guidelines
Conduct the interview in a well-lit room, separated from distracting noise, with a large table and comfortable chairs, and have coffee and munchies on hand.
Set a limit of 10 people or fewer for each interview.
Conduct separate interviews for users and management.
When you have to interview several groups of people, designate a group leader for each group.
Prepare your questions prior to the interview.
If you're not very good at taking notes, either assign that task to a dependable transcriber for each interview or get the group's permission to use a tape recorder to record the interview.
Give everyone your equal and undivided attention.
Keep the pace of the interview moving.
Always maintain control of the interview.

15. Mission Statements Mission Statement Guidelines
A well-written mission statement has the following attributes:
It expresses its point succinctly and immediately.
It avoids unnecessary statements or details and is well-defined.
It avoids phrases or sentences that explicitly describe specific tasks.
It makes sense to you (the database developer) and to those for whom you are designing the database.
The immigrant research database will support Melissa Estelle’s PhD project on people born and raised in Ireland and now residing in US or Canada/ Washington State or British Columbia. With this research the client is trying to look for changes in people after migrating to Canada or America.

16. Mission Objectives Mission Objective Guidelines
A well-written mission objective has the following attributes:
It comprises a declarative sentence that clearly defines a general task and is free from unnecessary details.
It expresses itself in general terms that are succinct, to the point, and unambiguous.
It makes sense to you and to those for whom you are designing the database.
To substantiate client’s PhD project.
To be able to easily extract information on differences between Irish born/raised US and Canadian residents or citizens.
To design the database in such a way that they remain flexible for future expansion.

17. TEAM PROJECT STRATEGIZE GROUPS
To Do:
Team Name
Team Member Info List (Names, s, Phone, Short Bio)
Team Leader?
Phase Leaders?
Construct to Send to Client to Set Up Interview Time
Construct of List of Potential Interview Questions
Who Will Conduct the Interview? Interviewer? Note Taker?
Working it Up in Team Site (or additionally something like Asana)
Document Types and Backup Plan

18. Projects and the Team Formations
Project A: PSYCHOLOGY
Denise Michaels   /
Office hours:  M/W/F 8-8:30am (or by appt. those afternoons)
Project B: WSMTA
Carol Karlak

19. TEAMS TEAM A: Psychology TEAM B: WSMTA Kidd, Brian Karlak, Carol
Damneun, Thongsaveui
Miller-Young, Tonweya
Miranda, Kat
TEAM B: WSMTA
Karlak, Carol
Handa, Manpreet
Ledina, Gunta
Ly, Nguyen

20. TEAM WORK
TEAM TIME: PHASE 1 Project Planning