2. Discussed DAU website

Comments included how very comprehensive it is and the many navigation possibilities. Comments about user-efficiency in navigation and forward thinking technology including itunes, podcasts and videos.

3. Deliverables

We have four deliverables, with two coming up right away. In one week, (Sept. 28), we present our front-end analysis to Kevin and On Oct 1, we present to the client. The second deliverable is due just 18 days after that. We have to have front end analysis report done by Friday so the weekend can be spent compiling. James and Sue developed a front-end analysis outline on Friday, utilizing readings and projects from EDIT 705 and our current courses.

4. Front-end analysis

Based upon General Anderson’s keynote speech, review of DAU website, and meeting with DAU today. From those things, we’ll draw our front-end analysis. Three elements that were present in every front end analysis that James and Sue reviewed were background, problem definition and strategy. (This is pretty much the proposal/SOW) and is under Part I of the Front End Analysis assignment plan. Part II includes preliminary findings – each team member will be assigned to research a section. Then, we will all collaborate as we combine our contributions into cohesive analysis. This will be incorporated into the Action Plan – which will direct our work.

Front-end Analysis outline (PDF)

We discussed the definition of Performance Analysis. PA breaks into Front End Analysis and Needs Assessment. Needs Assessment will then become the briefing report. It’s not as linear as Addie model; we recognize the process throughout will be fluid. Talked about First Things Fast and other recent reading assignments to help us define those terms. Also reviewed information and class discussion from Shahron’s class last week for that same purpose. The scope document will be related to problem definition. The consensus is that we need a scope document internally, even though we don’t know for sure if it will be a deliverable.

We need to ask the right questions to narrow the broad scope. We need to delineate scope and might put some of those items into a ‘future recommendations’ section of final report.

Nada came in briefly to confirm today’s DAU visit. A copy of the agenda was provided to her. A list of our questions for DAU is on Google docs right now. Nada counselled us to remember the list of questions and answers will be very important for our front end analysis. For today, website location will stay on wordpress site as it currently is, not switched to GMU site. Milestones highlighted in yellow on wiki version of syllabus have been posted under ‘deliverables’ on the wordpress site.

6. Assign Front End Analysis responsibilities based on project timelines

In addition to typing up your contribution to the FEA, give Ryan a slide on a plain white slide. Ryan will consolidate and style. Sue will do action plan (since she’s PM next time).

Front-end Analysis schedule (Word)

We will discuss our FEA research as it proceeds, but people assigned are the ones assimilating info and writing paragraph. Our plan is to me on Wednesday morning at 9:30 for preliminary discussion. As part of our research, we should each review keynote speech, review website, read some of the DAU journals on Tuesday and Wednesday. Thursday we will give presentations to each other about our individual FEA assignments.

We agreed to keep this Friday open in case we have more FEA analysis information to discuss. Have slides and paragraphs to Ryan by 8am Friday morning. He will send it out in completed form for us to review and prepare for our Monday presentation to Kevin and Nada.

Chose Arial font, 12 point for submissions

7. Select Open Source Project Management Tool

We chose Zoho, a free, social, web-based PM management tool. The free package includes one project, with unlimited users. Capabilities include tracking, planning and nice Gantt chart capabilities.