| 
  • If you are citizen of an European Union member nation, you may not use this service unless you are at least 16 years old.

  • Stop wasting time looking for files and revisions! Dokkio, a new product from the PBworks team, integrates and organizes your Drive, Dropbox, Box, Slack and Gmail files. Sign up for free.

View
 

IntraCor Meeting

Page history last edited by Yase Ge 10 years, 10 months ago

IntraCor Meeting-(Intranet Portals Team)

Quick Links: IntraCor Homepage, IntraCor Deliverable Page, Intranet Portal Wikipedia

 

Content



IntraCor Meeting One - Topic: The 1st Team Meeting

Quick Link: IntraCor Deliverable One

 

Attendees:

  • The Whole Team - Mustapha Oluwa,     Rob Jawor,     Peter Zucker,     Yase Ge

 

Time/Date/Tool:

  • 8-10 PM, April 17, 2009, Confirm with phone and the whole meeting through Skype

 

Agenda

  • Discussion for the team name
  • Discussion for the team logo
  • Discussion for the team collaboration tools
  • Discussion for the individual role in the team and the definition of the role responsibilities
  • Determine next meeting time

 

Notes

  • Team Name
    • Probably names: PrivNet -> Private Network; SCAL -> Stop Collaborate and Listen; Global IntraCor -> Global intranet for corporate office
    • After discussion and improvement, final: IntraCor -> Intranet Corporation
  • Team Logo
    • Probably Logos: about 11, exchange through the Skype sending file function
    • After discussion, the logo Intranet-2 excluded because it is similar to last team, then everybody lists his top two choices and vote
    • Logos selected for vote: Intranet, Collaborate Puzzle, Intranet-1, Intranet Portals and Intranet System
    • After vote, final: Collaborate Puzzle
  • Collaboration Tools
    • Methods of communication we have used email, Skype, phone and we plan to use Mind Meister and OfficeZilla
    • After discussion, we decide the main is OfficeZilla and we use Skype, Email, Phone and Mind Meister for assistants
  • Individual Role & Role Responsibilities (difficult part)
    • Individual Role
      • Original roles: Project Manager, Research Analyst, Web Master and Presentation Leader
      • After consulting, 4 roles change into 3, and there are Project Manager, Research Analyst and Web Master
      • Final: Project Manager - Mustapha Oluwa, Research Analysts - Rob Jawor & Peter Zucker, and Web Master - Yase Ge
    • Role Responsibilities
      • Obtaining some main points of every role
      • As an example: Looking at the cases, everyone of us does one case we are more efficient than sticking 100% to our role
      • Remain to be improved
  • Next Meeting Time
    • Next Tuesday April 21, 2009, expect to start at 9 PM

 

Action Items

  • Finalize and publish list of new features to PBwiki.com Web site (Yase Ge, by 4/18/2009)
  • Sign up and try OfficeZilla (Everyone, by 4/21/2009 before next meeting)
  • Play everyone's role and go on defining the role responsibility (Everyone, by 4/21/2009 before next meeting)

 

Back to top


IntraCor Meeting Two - Topic: A Short Meeting for Definition of Dimensions

Quick Link: IntraCor Deliverable Two

 

Attendees:

  • The Whole Team - Mustapha Oluwa,     Rob Jawor,     Peter Zucker,     Yase Ge

 

Time/Date/Tool:

  • 9-10 PM, April 21, 2009, Through Skype

 

Agenda

  • Discussion for the characteristics of dimensions
  • Discussion for the features of characteristics
  • Determine next meeting time

 

Notes

  • Characteristics of Dimensions
    • Question: what characteristics/features does our intranet portal need in order to be successful. What do users look for?
    • By discussion we come up with 8 characterisitics for our intranet portal dimensions
    • Final: the draft of the 8 characterisitics are

      1. Customization;  2. Security;  3. User Friendly;  4. Remote Access;

      5. Communication Methods;        6. Document Repository;

      7. Privacy Act/Code of Conduct/Mission Statement;   8. Blog.

  • Features of Characteristics
    • As assignments for the next meeting (see the detail in Action Items)
  • Next Meeting Time
    • This Friday April 24, 2009, expect to start at 9 PM

 

Action Items

  • Finalize and publish list of new features to PBwiki.com Web site (Yase Ge, by 4/22/2009)
  • Write a few ideas to each characteristic and exchange by email (Everyone, by 4/24/2009 before next meeting)
  • Needs to take care about his two characteristics, and makes a Summary at next meeting (Everyone, by 4/24/2009 at next meeting)
    • Rob:       1. Customization; 2. Security;
    • Yase:      3. User Friendly; 4. Remote Access;
    • Peter:     5. Communication Methods; 6. Document Repository;
    • Mustapha:  7. Privacy Act/Code of Conduct/Mission Statement; 8. Blog.
  • Play everyone's role and go on defining the role responsibility (Everyone, the Unfinished Item in the 1st meeting)

 

Back to top


IntraCor Meeting Three - Topic: Discussing the Dimensions

Quick Link: IntraCor Deliverable Two

 

Attendees:

  • The Whole Team - Mustapha Oluwa,     Rob Jawor,     Peter Zucker,     Yase Ge

 

Time/Date/Tool:

  • 9-11 PM, April 24, 2009, try dimdim first, through Skype, try to use MindMeister, but it is currently down for maintenance

 

Agenda

  • Discussion for the dimensions
  • Determine next meeting time

 

Notes

  • Dimensions
    • The discussion follows the instruction on the FAQ of COL web (the content is attached below)
    • We are entangled with the issue of definitions of activities and dimensions
    • What we got so far:

      The purpose for building the IntrCor intranet portal with emphasis on customization, security, user friendly, remote access, communication methods, document repository...is:

    1. Customization: Click & drag, color scheme, preview boxes. Ability to add in content relevant to the user.  Similar to iGoogle.

      Low – Static pages with little customization other then color and font preferences.  Page content determined by company not individual.

      Medium – Ability to place multiple company approved applications and content pages to the Intranet Portal.

      High - Can add multiple sources of internal and external content.  Also, ability to code new applications.

    2. Security: This is the ability for an individual (company) to be able to protect the company from attacker and hacker that want to penetrate the company confidential information.

      Low – Open access for all employees and outside vendors to view.  Prevent open access to entire internet.  No login required but VPN connection is needed for outside access.

      Medium – Allow access to internal employees.  User must use regular ID and Password to obtain access.  Ability to reset own password.

      High - Forces users to obtain username/password for access with special characters for enhanced security.  Provides file-level encryption.  Only admin accounts have permission to add, delete, modify content.

    3. User Friendly: easy to use without any problem, not harm user’s work and not waste user’s time.

      low - multiple language support, multi browser support,

      mid - good GUIs (Graphical User Interfaces), good human–computer interaction,

      high- no coding involved, solid searchable help section, and feedback system.

    4. Remote Access: allow some part of Intranet for some users to be able to access from a far distance with ease. (Important Data excluded)

      low - security log in and Remote Access Sessions may terminate after a set time limit.

      mid -  accessible through HTTPS, web browser access for the data.

      high - accessible through VPN , remote desktop connection or desktop sharing access for the applications.

    5. Communication Methods: To establish an organized communication between authorized parties by using available communication methods.

      Low-message/discussion board, announcements

      Mid-contacts, chat, email

      High-video conference

    6. Document Repository: To support various file formats, and organize them in a indexed document achieve.

      Low-address book, calendar & reminder function, user manual

      Mid-search, file transfer, shared folders, e-library, search

      High- backup, SharePoint, time/date stamp + version control, access logs

    7. Privacy Act/Code of Conduct/Mission Statement: These are principles and guidelines that guide the business and employees in the day to day operation.

      Low: Warning

      Mid: Suspension

      High: Terminate

    8. Blog: To introduce a section where employees are able record and describe the day-to-day events and allow readers to contribute through comments.

      Low - Add new post who is “web”/intranet master, recent posts, recent comments, purpose (explanation)

      Mid - Six months of past history with search capability for specific topics, categories, reply section

      High - integrated IM/VoIP, posting multimedia

  • Next Meeting Time
    • This Saturday April 25, 2009, expect to start at 9 PM

 

Action Items

  • Finalize and publish list of new features to PBwiki.com Web site (Yase Ge, by 4/25/2009)
  • Send email to Professor for asking the definitions of activities and dimensions (Rob and Peter, by 4/24/2009)
  • Play everyone's role and go on defining the role responsibility (Everyone, the Unfinished Item in the 1st meeting)

 

Dimensions (the FAQ on COL web)

What do we mean when we say the dimensions of interaction?

  • a. These are the important factors that need to be considered when planning for or implementing a technology solution for collaboration.
  • b. These do not fall within one category – group task, or technology affordances (things it can do), or access methods (web vs. server) or the complexity (does it do one thing or all things that you think you will need?). You should explore all of them.
  1. Your group should start with exploring diverse activities that could occur within your topic area. How could people do things in your topic area? Brainstorm a list of 10-12. Make them as different from one another as you can (this will make your Use Cases better).  Keep them rather general (don’t try to be extremely specific at this point). Think about time and space think about membership; think about divergent tasks within the activity. Think about conditions (single culture: single language, single/multi-time zone, single/multi-organizational, security, IP issues, the list goes on and on – don’t limit yourselves!!) The more diversity the better.
  2. Next choose the top 5 or 6 of the activities—making sure they are as different as possible from one another. And then look more closely at one. Begin to think about what technology you will need to support this activity. What does the software/tool have to be able to do to help people do this activity under your chosen conditions? These, along with your conditions are the dimensions we have been talking about. Now do the same thing with the remaining 4 or 5 activities. You may find that there are common elements, and hopefully, you will find there are differences.
  3. A MindMapping tool is very helpful for this activity (like MindMiester)
  4. Once you have your focused list, now look at them and see if you can identify the range for that category. For example, let’s say that cost is one of your items. The range can be from low cost (open source, but may require more internal support to implement and keep running) to mid range (low cost per seat, and some cost for support) to very high (high initial cost, but training and support may be included).[BTW – cost is usually NOT a good dimension as it is too vague]
  5. Next review you list of dimensions. Choose the top 6 or 8 (again we are looking for diversity here but don’t drop an important dimension just to make the list different).
  6. Your deliverable is to give us your list of activities (with a short – no more than 1 short paragraph—description) and the associated list of dimensions (with a one line descriptor).

Next week you will be selecting 4 of your activities and developing them further into full Use Cases. This activity is supposed to help you focus your thoughts toward that end. Try to avoid voting as a means to reducing your list but instead use persuasion and build consensus. It may take you a little longer but is a VERY valuable technique to get a handle on.

You may end up adding some of the more minor leaf elements back into your Use Cases but they will be focused around your main leaves/cells. 

 

Back to top


IntraCor Meeting Four - Topic: Go on with Discussing the Dimensions

Quick Link: IntraCor Deliverable Two

 

Attendees:

  • Only Three - Rob Jawor,     Peter Zucker,     Yase Ge
  • Not attend - Mustapha Oluwa ("I could not attend the meeting because I went out in the afternoon hoping to reunrn early. Unfortunately I was caught up in the rain")

 

Time/Date/Tool:

  • 9-12 PM, April 25, 2009, through Skype, use MindMeister for a while.

 

Agenda

  • Go on the discussion for the dimensions
  • Determine next meeting time

 

Notes

  • Dimensions
    • We receive the replies from the Professors. Generally, the items listed in last meeting are NOT activities, these are dimensions and activities would be things that companies use Intranet portals for. And the deliverable will look like this:

      Actvitiy 1 (Paragraph description of it)

      * Requirement sentence

      * Requirement sentence

      * Requirement sentence

      * Requirement sentence

      * Requirement sentence

    • With discussion, We consider that we have had Description of Dimensions, but we don't have 5 or 6 of the activities (making sure they are as different as possible from one another)

      So we try to find the activities, at end we get 5 activities and make a Matrix for the relation of the activities and the Dimensions

    • All the works are in the IntraCor Deliverable Two
    • We are still entangled with the issue of definitions of activities and dimensions, and it takes us very long time.
  • Trouble
    • In this meeting that we had difficulty (even more after our professors emails) in understanding dimensions and activities.
    • We were not sure about the relation form and the range in the Dimensions Matrix.
  • Next Meeting Time
    • Next Tuesday April 28, 2009, expect to start at 9 PM

 

Action Items

  • Finalize and publish list of new features to PBwiki.com Web site (Yase Ge, by 4/26/2009)
  • Play everyone's role and go on defining the role responsibility (Everyone, the Unfinished Item in the 1st meeting)

 

Back to top


IntraCor Meeting Five - Topic: A Short Meeting for Use Case

Quick Link: IntraCor Deliverable Three

 

Attendees:

  • The Whole Team - Mustapha Oluwa,     Rob Jawor,     Peter Zucker,     Yase Ge

 

Time/Date/Tool:

  • 9-10 PM, April 28, 2009, Through Skype

 

Agenda

  • Discussion for use case
  • Determine next meeting time

 

Notes

  • Use Case
    • Question: Which 4 activities we should choose from our activities?
    • By discussion we exclude the Access Point for Employees, and keep the Tools & Resources, Associate Services, Business Operations, and Company Calendar
    • Finally, everyone picks up a activity and prepares the case for discussing at next meeting (see the detail in Action Items)
  • Next Meeting Time
    • This Friday May 1, 2009, expect to start at 9 PM

 

Action Items

  • Finalize and publish list of new features to PBwiki.com Web site (Yase Ge, by 4/29/2009)
  • The below list is the assignment of each member; write a draft case of the activity and exchange by email (Everyone, by 5/1/2009 before next meeting)
    • Peter:    1. Tools & Resources;
    • Rob:      2. Associate Services;
    • Yase:     3. Business Operations;
    • Mustapha: 4. Company Calendar.

 

Back to top


IntraCor Meeting Six - Topic: Determination of 4 Top Use Cases

Quick Link: IntraCor Deliverable Three

 

Attendees:

  • The Whole Team - Mustapha Oluwa,     Rob Jawor,     Peter Zucker,     Yase Ge

 

Time/Date/Tool:

  • 9-11 PM, May 1, 2009, Through Skype

 

Agenda

  • Discussion for 4 use case drafts
  • Determination of 4 top use cases
  • Determine next meeting time

 

Notes

  • 4 use case drafts
    • Exchange the drafts, correct grammar, amend word used and propose adding or deleting bullet point
  • 4 top use cases
    • Unify the cases format and style, control the length of cases and add picture for each case
  • Next Meeting Time
    • Next Friday May 8, 2009, expect to start at 9 PM

 

Action Items

  • Finalize and publish list of new features to PBwiki.com Web site (Yase Ge, by 5/2/2009)
  • Check the use cases on the PBworks' webpage IntraCor Deliverable Three, make a change if needed (Everyone, by 5/3/2009)

 

Back to top


IntraCor Meeting Seven - Topic: A Short Meeting for Available Tools

Quick Link: IntraCor Deliverable Four

 

Attendees:

  • The Whole Team - Mustapha Oluwa,     Rob Jawor,     Peter Zucker,     Yase Ge

 

Time/Date/Tool:

  • 9-11 PM, May 8, 2009, Through Skype

 

Agenda

  • Discussion for available tools
  • Determine next meeting time

 

Notes

  • Available Tools
    • Exchange the drafts, create the a spreadsheet on PBworks and input 40 tools we have found
    • Assign 10 of 40 to each member (see the detail in Action Items)
  • Next Meeting Time
    • Next Friday May 15, 2009, expect to start at 9 PM

 

Action Items

  • Finalize and publish list of new features to PBwiki.com Web site (Yase Ge, by 5/9/2009)
  • The below list is the assignment of each member; finish the company, URL, matchable cases, price and a short description of feature on the PBworks' webpage IntraCor Tools, make a change for the sheet if needed (Everyone, by 5/15/2009 before next meeting)
    • No. 01-10: Yase Ge;
    • No. 11-20: Peter Zucker;
    • No. 21-30: Rob Jawor;
    • No. 31-40: Mustapha Oluwa.

 

Back to top


IntraCor Meeting Eight - Topic: Available Tools

Quick Link: IntraCor Deliverable Four

 

Attendees:

  • The Whole Team - Mustapha Oluwa,     Rob Jawor,     Peter Zucker,     Yase Ge

 

Time/Date/Tool:

  • 9-11 PM, May 15, 2009, Through Skype

 

Agenda

  • Discussion for available tools and the Suitable tool for each case
  • Discussion for making up the use cases
  • Determine next meeting time

 

Notes

  • Available Tools and The Suitable Tool for Each Case
    • Complete all the infotmation for the 40 tools in webpage IntraCor Tools; choose the most suitable tool for each case
  • Making up the use cases
    • Discuss the problem of Use Case Four and the Must Haves which should be more descriptive and include some measure
    • Make up each case (see the detail in Action Items)
  • Next Meeting Time
    • Next Tuesday May 19, 2009, expect to start at 9 PM

 

Action Items

  • Finalize and publish list of new features to PBwiki.com Web site (Yase Ge, by 5/16/2009)
  • Rewritten the Use Case Four more clearly (Mustapha, by 5/19/2009 before next meeting)
  • Make a change for everyone's Use Case if needed; when the change is made, highlight it and tell Rob or Peter which case is done by email (Everyone, by 5/19/2009 before next meeting)
  • When all the changes are done -Rob or Peter receives all the others' emails-, send a email to the Professor (Rob, Peter, by 5/19/2009 before next meeting)

 

Back to top


IntraCor Meeting Nine - Topic: A Short Meeting for Presentation and WikiPedia Page

Quick Link: IntraCor Presentation, IntraCor Wikipedia

 

Attendees:

  • The Whole Team - Mustapha Oluwa,     Rob Jawor,     Peter Zucker,     Yase Ge

 

Time/Date/Tool:

  • 9-10 PM, May 19, 2009, Through Skype

 

Agenda

  • Discussion for presentation and the two use cases of presentation
  • Discussion for wikiPedia page
  • Determine next meeting time

 

Notes

  • Presentation and Two Use Cases
    • Two members of team will prepare the slides of the presentation and one of them will do the presentation in class (see the detail in Action Items)
    • The Use Case Two - Associate Services and the Use Case Three - Business Operations are selected for the presentation by vote
  • WikiPedia Page
    • Other two members of team will prepare the wikiPedia page (see the detail in Action Items)
  • Next Meeting Time
    • Next Tuesday May 26, 2009, expect to start at 9 PM

 

Action Items

  • Finalize and publish list of new features to PBworks.com Web site (Yase Ge, by 5/20/2009)
  • Prepare the presentation (Rob, Peter, by 5/26/2009 before next meeting)
  • Prepare the wikiPedia page (Mustapha Oluwa, Yase Ge, by 5/26/2009 before next meeting)

 

Back to top


IntraCor Meeting Ten - Topic: Presentation and WikiPedia Page

Quick Link: IntraCor Presentation, IntraCor Wikipedia

 

Attendees:

  • The Whole Team - Mustapha Oluwa,     Rob Jawor,     Peter Zucker,     Yase Ge

 

Time/Date/Tool:

  • 9-10 PM, May 26, 2009, Through Skype

 

Agenda

  • Discussion for presentation
  • Discussion for wikiPedia page
  • Determine next meeting time

 

Notes

  • Presentation
    • After discussion add one slide about available tools in slides of presentation
  • WikiPedia Page
    • After discussion determine edit a existent page Intranet portal on wikipedia
  • Next Meeting Time
    • Next Friday May 29, 2009, expect to start at 9 PM

 

Action Items

  • Finalize and publish list of new features to PBworks.com Web site (Yase Ge, by 5/27/2009)
  • Prepare the wikiPedia page (Mustapha Oluwa, Yase Ge, by 5/26/2009 before next meeting)

 

Back to top


IntraCor Meeting Eleven - Topic: Final Meeting

Quick Link: IntraCor Presentation, IntraCor Wikipedia

 

Attendees:

  • Only Three - Rob Jawor,     Peter Zucker,     Yase Ge
  • Not attend - Mustapha Oluwa

 

Time/Date/Tool:

  • 9-10 PM, May 29, 2009, Through Skype

 

Agenda

  • Discussion for presentation
  • Discussion for wikiPedia page

 

Notes

  • The group work is in good shape.
  • Ready to do the presentation.

 

Action Items

  • Finalize and publish list of new features to PBworks.com Web site (Yase Ge, by 5/30/2009)
  • Go to Classroom, Attend Presentation Session - CDM Center Room 801 (Everyone, 6/01/2009 at 5:45 PM)

 

Back to top


 

Comments (0)

You don't have permission to comment on this page.