Docstoc
EXCLUSIVE OFFER FOR DOCSTOC USERS
Try the all-new QuickBooks Online for FREE.  No credit card required.

Wikispaces

Document Sample
Wikispaces Powered By Docstoc
					Virtual Teams in Action
                         Team C:
                       Casey Lyells
                       Stefeni May

                        John Munn

                  Ryan Reichenbach
                   Eileen Sparhawk
     Team C: The Final
Project - Virtual Teams
    Using a cloud tag for analysis,
 determine the foci and themes for
   each class forum discussion for
           weeks 1, 2, 3, 4, and 5.
The final class project scope includes defining the
methodology used to establish the virtual team and
production of 5 Tag Clouds

     Build a tag cloud for each class forum - Weeks 1 - 5
      Include information that supports a content overview
       of the key terms for each week
    Answer the following questions in our final
     report/presentation:
       1.   How will you organize?
       2.   How will you communicate and collaborate?
       3.   How will you assign roles?
       4.   What life-cycle methodology will you use?
       5.   How will you document your methodology?
       6.   What technologies, tools, and/or platforms will you
            implement?
       7.   What virtual strategies will you use?
       8.   How will you document and report your results?
       9.   How will you know that you achieved the project goal?
Key team decisions and guidelines were
approved. Leadership was transitioned
between project phases

 1.   All tasks will distributed to team members evenly
 2.   Bulk of the work will be performed using Web 2.0
      Technologies, no face-to-face meeting will occur
      during the project life cycle.
 3.   The final product will be presented in PowerPoint.
 4.   Eileen will lead initial project set up and virtual
      team strategy
 5.   Ann will manage communication and compile final
      presentation
 6.   Ryan will manage the building of the Tag Clouds
Team C was organized around job
skills and task assignments
   Ryan was the IT specialist and was assigned
    the production of the Tag Clouds
   Ann took the lead on the final presentation
    development and team communication
   Eileen build the project schedule
   Casey documented scope and strategy
   John tested additional tag cloud software
   Stefeni tested and established a team wiki
Communication and
Collaboration
   Weekly Check-in Conference Calls
       Participating teammates post notes to wiki
         Non-participating teammates ask clarifying questions
          via wiki discussion board
   Created wiki on wikispaces.com
       Primary tool for communicating
         Discussion threads for differing topics

         All teammates have the same editing privileges

         All documents and revisions are uploaded and stored

   DU Email Accounts/University College
    Discussion Board
       Used as backup communication
Role Assignments
      Role assignments
              By Phase
How We Assigned Roles

•   We assigned roles in three phases, during which
    roles were assigned in a volunteer and appointment
    manner
       First, we discussed initial group roles during week 7 in
        the threads.
          From this we decided who will be handling our
            technical lead for the tag clouds
       During the second week we had a conference call
        where we volunteered to be phase/process leaders.
       Eileen assigned the remaining jobs/roles during her
        production of the project schedule
Process/Development Phase
Tag Cloud Development
Presentation Development
Methodology and
 Documentation
      Waterfall Model
Life Cycle Methodology
   Requirements
    Team reviewed assignment and discussed on University College thread with
    instructor input.

   Design
    Team agreed design consists of PowerPoint presentation summarizing virtual team
    efforts and required deliverables of five (5) tag clouds summarizing class discussions
    for weeks one (1) through five (5) of the course.

   Implementation
    Tasks identified and assigned to team members. Tools selected, tag clouds
    generated and PowerPoint presentation compiled through group effort.

   Verification
    Team meeting to review deliverables compared against design.

   Maintenance
    Corrections and modifications made based on output from verification.
A “Waterfall Model” life cycle methodology was
integrated into the Microsoft schedule work
breakdown
Lifecycle Methodology
continued
Team methodology and guidelines were
documented and filed on the team wiki
space

Wiki work space included:
 Project schedule
 Project strategy- Waterfall methodology and
  team guidelines
 Scope definition
 Decision and action log
 Ongoing communication topics
 Document files with version control
Technologies, Tools &
Platforms
   UCOLLEGE Platform
   Conference Calls
   Wikispaces
   Email
   Tag cloud generator. Open source PHP/XML web
    application developed by Chirag Mehta using Porter
    Stemming Algorithm. Implemented at:
    http://www.firsttrackssoftware.com/firsttracks/tagline/
    ORL4570.html
Virtual Strategies Employed
   Conference Calls
       Held on a weekly basis
       Used to check in with teammates and progress
   University College Discussion Board/Team C
       Initially used as main forum for team communication until
        Team C wiki was created
   Team C Wiki – www.wikispaces.com
       Discussion Boards – created new thread for topics
       Documents uploaded to documents area
         Posting teammate notified other members when posting
Documentation of Results
   Tag cloud generator application acquired and installed.
   Code modified as necessary to run on PHP 4.
   Team organized/structured, developed scope, strategy, and WBS,
    assigned tasks, and distributed documentation.
   Presentation template developed and distributed.
   Team instructed on XML data format required by tag cloud generator.
   Content collected from weeks one(1) through five(5) discussion forums
    and formatted to instructions.
   Tag clouds generated from collected data using tag cloud generator.
   Tag clouds reviewed, generator settings modified to eliminate “virtual”
    from dominating results, reduction in word summary, and increase in
    font.
   Presentation completed with completed content.
   Presentation reviewed and verified.
   Maintenance performed based on output from verification.
How We Will Know We
Achieved Project Goal



   We will perform a scope verification to
    determine if we achieved our project goal.
 Final Team Project
  Tag Clouds and Overview of
Weeks 1 – 5 Discussion Boards
Week 1 Cloud Tag
Week 1 Foci & Themes
   Introductions
       Though Not Weighted, Some Focus was on Getting
        Acquainted with Classmates
   Virtual Environments & Virtualization
       Defining the Term, “Virtual”
           Abstraction of Reality
           Traditional Model vs. The New, Global Model
       Defining the Term, “Virtualization”
           Infrastructure and Collaborative Tools
            (Technology)
           A New Paradigm
Week 1 Foci & Themes
    Why Virtualize?
        The Global Marketplace
    How to Virtualize
        Infrastructure and Tools
        Attitudes and Training
    The Issue of Trust
        Control
        Maintaining Quality Standards
        Swift Trust
Week 2 Cloud Tag
Week 2 Foci & Themes
   Reasons teams seek to organize
    virtually
       Accountability
       Collaboration
       Documented work
       Globalization
       Economical
   Virtual organizing  information marketplace/
    electronic bazaar
       Geographically dispersed talent
       Emerging ideas and engaging a large population
       Increased productivity
Week 3 Cloud Tag
    Week 3 Foci & Themes
   What is cyber leadership?
       Leadership in a virtual environment:
         Across geographic locations
         Across time zones
         In a global marketplace
         Across corporate boundaries
       Acknowledges generational and cultural differences
   What are the attributes of “cyber-leadership?”
       Traditional leaders plus advanced technology skills (email, blogs, wikis, etc.)
       Provides a dynamic work space
       Proactively involved
       Demonstrates appropriate behaviors
       Understands team dynamics
   A cyber-leader
       Motivates team members
       Removes barriers and inspires productivity
       Values teammates and builds trust
       Facilitates collaboration and communication
       Keeps team members connected
       Holds team members accountable
Week 4 Cloud Tag
    Week 4 Foci & Themes
    Week 4’s discussion centered around three main questions;
    1. Can trust exist in global virtual teams where the team members
       do not share any past, nor have any expectation of future,
       interaction?
    2. How might trust be developed in such teams?
    3. What communication behaviors may facilitate the development of
       trust?


                                The six most common words
                                used were:
                                Behaviors, Global, Interaction,
                                Leader, Teammates, and
                                Trustworthy
Week 4 Foci & Themes
   After reviewing week four’s discussion and using this
    tag cloud there were several themes that emerged.
       First, trust (or the act of being trustworthy) is a necessity to
        teams and is needed across all cultures or in other words is
        global.
       Second, trust is easy to build if it is modeled, demonstrated,
        and established by the leader early on in the process or
        interactions of the team.
       Last, as teammates interact with each other our trust is slowly
        built (and can be rebuilt if necessary) through our interactions
        with each other, and is best built over time but can be built
        quickly early on.
Week 5 Cloud Tag
Week 5 Foci & Themes
Focused on reviewing and assessing virtual teams using the
System Design Life Cycle (SDLC) methodology



          Virtual teams should use a life cycle based methodology
           that manages the project through all of its phases, from
           initiation through implementation

                This methodology ensures stakeholders needs are met
                This methodology supports software design

          There are various iterations of the life cycle methodology
           approach. Winston Royce developed the first SDLC,
           known as “The Waterfall” model in 1970.
           http://isedj.org/isecon/2003/3212/ISECON.2003.Conn.pdf
Week 5 Foci & Themes
Focused on reviewing and assessing virtual teams using the
System Design Life Cycle (SDLC) methodology

   Inspired Agile methodology used in software
    development http://agilemethodology.org
   The Waterfall methodology manages incremental
    changes and ensures values by building to design
    requirements
   The iterative nature of product/project development
    requires constant attention and management from
     a leader to ensure communication is effective
    and the virtual team remains productive
    http://www.computerworld.com/developmenttopics/development/story/0,108
    01,71151,00.html
Overall Focus for Weeks 1-5
Scope Verification
Scope:
1. Build a Tag Cloud and summary for Virtual
    Class discussions Week 1 through Week 5.
Eileen          John           Ann
Stefeni         Casey          Ryan

1.  Answer all Dr. Conn’s questions in the
    project definition
Eileen            John          Ann
Stefeni           Casey         Ryan

				
DOCUMENT INFO
Shared By:
Categories:
Tags:
Stats:
views:7
posted:7/21/2012
language:
pages:36