Final Presenation:
TTACTeamFall2007Presentation1201007Combined1.ppt
TTACTeamFall2007Presentation1201007Combined.ppt
Gliffy graphics:
Okay ... here is a gliffy based on the current usage of video conferencing based on Shuangbao's feedback: http://www.gliffy.com/publish/1334954/
... and here is one just detailing adobe connect: http://www.gliffy.com/publish/1334975/
And finally ... the ideal scenario with Movi included. I decided to keep the codian bridge because if we are going with the ideal, then we might as well go all the way: http://www.gliffy.com/publish/1334971/
I think that is a great idea ... it will drive the point home and make for a smooth transition into the realistic situation that we detail ....
In the notes for slide 20 where Afua talks about the Needs Analysis Findings, I noticed that it said the following:
After exploring audience needs and the affordances of available communication tools, members of the immersion team discussed with the client implementation issues with respect to the envisioned virtual collaboration center. These issues involve constraints imposed by factors such as bandwidth, browser requirements, system incompatibilities, and needs for human technical support that exceed what is currently available. The client acknowledged that it may not be possible to implement some features of a virtual collaboration center until technical issues that are beyond the control of the immersion team are resolved. The division of ownership, control, and rights of use of available resources among multiple organizations was also discussed as a possible barrier to implementation. The client reiterated a desire to take a long-term view and indicated that the team should not view current ownership and licensing issues as unalterable constraints to providing some immediate solutions.
Should this actually be something that Rahel mentions to transition from the ideal to the realistic? What do you guys think? KA
TTACTeamFall2007Presentation120807Combined.ppt
I went through the presentation to make sure that the font sizes were as consistent as possible and for spelling etc. I noticed that we had Tandberg Management Suite listed on slides 22 and 23. I combined it onto 22 and removed it from 23. I also have added in the references--now three pages.
On Monday, we'll need to add the links to the gliffy slides that Kim M. and Rahel are creating/updating.--KA
TTACTeamFall2007Presentation120707Combined-3.ppt
TTACTeamFall2007Presentation120707Combined-2.ppt
TTACTeamFall2007Presentation120707Combined.ppt
43 slides!
matthewSlides.ppt
My section of the presentation- Afua:
TTACTeamFall2007Presentation-Afua.ppt
TTACTeamFall2007Presentation120607LastSection6.ppt
Here is the last section with the updates we talked about today. I left space for the three variations of the gliffy graphics and for Marlena's scenario. I put two pages in for the References since I think that our list is long. Thanks--KA
Video_Conferencing_at_T-TAC-1.jpg
Okay ... here's mine:
TTACTeamFall2007Presentation_kmonti.ppt
TTACTeamFall2007Presentation120507.ppt
Here are the slides after our conference call this morning. Have fun in the snow. KA
TTACTeamFall2007Presentation120407.ppt
I populated the tools chart pages.
TTACTeamFall2007Presentation120207.ppt
Team--I have included more slides and put the strengths and challenges in the notes. I thought that might be more diplomatic than having actuals slides that say strengths and challenges.
In Google docs, I did not see a way to include notes...in fact the notes that were already on the PowerPoint seemed to have disappeared in Google docs. Please point out to me where they are in Google docs, if I am missing them. So...I did the updates in PowerPoint and uploaded it here.--KA
TTACTeamFall2007Presentation.ppt
Team--Here's the first crack at the final presentation that we need to give on December 10. Feel free to start the list of things that need to be added or edited here for us to discuss as time gets closer to the end of the semester.--KA
Strengths and challenges through the process:
KM--Love what you have written in the strengths and challenges section. Seems like you have his the nail on the head.--KA
How we started
Given the broad task to, "do something with T/TAC Online"
Strengths: Began with team building and developed norms, ground rules, and team roles
Team roles for analysis phase: http://immersion.gmu.edu/ttac/fall2007/roles.pdf
- We also spent the time getting to know more about eachother and identify how best we could proceed as a team-Afua
Challenges: Couldn't adequately develop our vision/mission and team goals since we really didn't know what our project focus was going to be
Review of Performance Analysis
Subject Matter Experts
Strengths: We talked to alot of people and gathered alot of valuable information
Challenges: This information pointed to such varied information about what we should focus our efforts on, we were lost in the jungle without a compass
Findings
Strengths: We came up with some very interesting recommendations, and each could take us in very different directions based on what we wanted to focus on.
Challenges: Each recommendation seemed just as important as the next -- how do we prioritize???
Recommendations
Strengths: After the meeting with the client, we were able to prioritize and recommend next steps.
Challenges: How would we be able to gather the right information in the needs analysis to inform the correct path in the design phase? Our focus was on developing a virtual collaboration center through T/TAC Online - how can we adequately address the diverse needs of the audience through the VCC?
Review of Needs Analysis
Subject Matter Experts/Target Audience
Strengths: We were able to identify an audience within an audience -- the technology opinion leaders within T/TAC (AT PP) with the idea that the concept of the VCC would diffuse to other T/TAC staff.
Challenges: Would limiting the VCC to the AT PP adequately address the greater needs of T/TAC? Is the VCC truly the best solution to meet the needs of T/TAC?
Trying to schedule meetings with them was difficult since they had busy and varying schedules. -Afua
Personas
Tools Analysis
Strengths: Was an exctiting period since we had the chance to "play" with some of the tools that we were not familiar with- Afua
Challenges: Understanding all the complexities involved in the existing systems and tools available to T/TAC was a siginficant challenge. SME referred to different tools and their capabilities in different ways. Understanding the implementation issues for each tool was also a challenge. This took several meetings with GMU staff and a continual pulse check to verify our understanding.
Findings
Strengths: Developing the VCC will allow the AT pp and other T/TAC members to meet and collaborate virtually.
Challenges: There are technical limitations such as firewalls, required web-browsers, disparate computer equipment, and human intervention on the back-end that would make it difficult for the Virtual Collaboration Center to operate seamlessly
Recommendations
Strengths:
Challenges:
Next Steps
Strengths:
Challenges:
Comments (0)
You don't have permission to comment on this page.