Jennifermai73's Blog

Just another WordPress.com weblog

D#15, HW#2 – Reflection April 21, 2010

Filed under: Deadline #15,Reflection — jennifermai73 @ 6:46 am
  • What were the steps you took to complete the project? How might you change your process if you were to complete the project again? What steps do you think you will take for your next project?

The final written report was a lot easier to complete because we had come up with a task list in the proposal.  So, everyone knew what they were responsible for.  Everyone completed their part and we compiled it all into one report.  If I were to complete this project again and for my future projects, I think I will try to make stricter deadlines.  While everything was completed on time, it was hard to get our schedules together.  We all have other classes, work, and finals.  Sometimes we had wait awhile for everyone to find the time to work on the project.

  • What are you most proud of in this project? Why are you proud? What are you most concerned with in this project? How did you try to address that concern before finally submitting your project? If you had more time, how might you further work on that concern?

I’m most proud of how well our group worked together. It was probably the best group experience I’ve ever had.  As for concerns, we focused a lot of the technical aspects of the paper; format, charts, and appendices.  I’m concerned that maybe we didn’t address the problem thoroughly.  If we had more time, I would further evaluate the PMT’s… and possibly check reviews from actual users since two of the applications we couldn’t’ test out since they had to be paid for.

  • In terms of learning about composing, what did you specifically work on to improve during this project? Do you feel you succeeded in improving your composing processes or skills? What composing processes or skills will you work on during your next project?

I really wanted to work on improving my collaboration skills.  Usually when I am in a group, I assume the role of the leader just to ensure that everything gets done correctly.  So, for this project, I just tried to assist the group in any way possible instead of being the one to delegate tasks.  For future projects, I want to work on composing tasks list and charters.  Osmara did a fabulous job constructing ours and I would like to be able to learn from her.

  • What course outcomes did you work towards during this project? Do you feel you achieved them? How do you know? What evidence does either your process or product for this current writing provide towards demonstrating your achievement of a course outcome? What outcomes do you think you will work on in your next project?

For this project I worked on realizing that it takes multiple drafts to create and complete a successful text.  I definitely feel that I achieved that outcome because we all came up with our own versions of drafts for the final project and collaborated together to incorporate all of our ideas.  For future projects, I’d like to work on understanding and applying legal and ethical uses of information and technology including copyright and intellectual property.  It’s probably the only outcome I did not work on this semester.

 

D#15, HW#1 – Final Report April 21, 2010

Filed under: Deadline #15,Projects — jennifermai73 @ 6:46 am

An Evaluation Report

From: Group 1 TWC 301

To: Dr. Shelley Rodrigo, CIO

GEEK TECH UNIVERSITY IT DEPT

TABLE OF CONTENTS

EXECUTIVE SUMMARY    3
INTRODUCTION    4
DEFINING THE PROBLEM    5
CRITERIA    7
DISCUSSION OF OPTIONS    8
COMPARISON    9
CONCLUSIONS    10
FINAL RECOMMENDATIONS    11
REFERENCES    12
APPENDIX    13

EXECUTIVE SUMMARY
Due to the continued expansion and growth of Geek Tech University, the GTU IT Department submitted a proposal requesting permission to review different project management tools (PMTs).  The PMT would enable the department to streamline IT communications, allow data transfer between departments and facilitate file transfer.  Current flow of information in the existing system is hindering the daily operations of several departments as well as creating unnecessary expenditures.
The IT Department received a positive response to the proposal request and evaluated three PMTs to determine the best application to fulfill GTU needs.  Four GTU technicians were asked to evaluate specific functions within each of the PMTs.  PMTs were evaluated for ease of use, management features such as file transfer capabilities and implementation costs.
After conducting a usability study of three PMTs, the GTU IT Department has determined that Smartsheet provided the features most beneficial to its needs.  Smartsheet allowed the technicians to communicate using the PMT and complete all of the tasks as assigned in the most time efficient manner.
It is the recommendation of the GTU IT Department that GTU secure the services of Smartsheet.  By using a centralized and web-based communications and information system project deadlines were met or exceeded through specific task management, file sharing was simplified and interdepartmental communication and overall productivity was improved.

INTRODUCTION
The purpose of this evaluation report is to provide information regarding the usefulness of online project management applications in assisting with the completion of large-scale projects at the GTU IT Department
At the request of the GTU IT Department, Project Management Tools were evaluated in order to alleviate data management concerns including:

•    Database security
•    Loss of accountability
•    Version-control issues  of documents and files
•    File disorganization
•    E-mail communication
•    Failed updates or missed file transfers
•    Miscommunication within department personnel
•    Meeting project deadlines
•    Task Management

Three PMT web based sites were chosen for evaluation: Basecamp, Zoho and Smartsheet.  The applications were chosen for their advertised potential of meeting the IT department needs. The functions the IT department specifically sought to utilize included:

•    Code-encrypted file sharing
•    Web-based mass storage and access
•    Email notifications
•    Deadline and meeting alerts
•    A history-tracker for changes made to documents and projects
•    User-friendly templates
•    Calendar functions

A usability team of IT technicians was created to evaluate the chosen PMTs based on the criteria as listed above.

DEFINING THE PROBLEM
The GTU IT Department has grown threefold over the last 5 years.  It is one of the largest university-based IT support teams in the US, employing over 300 employees nationwide.  The financial impact of our exponential growth has been very positive, but has presented the IT Department with operational challenges.  Under the antiquated project management system (GeekWorks 2.1) in place since 2008, we are unable to effectively manage and support large-scale projects within the department.  Our entire staff, especially those in remote locations, have expressed valid concerns with communication and task management relative to the current system.
As a result, The GTU IT Department has suffered a decline in productivity due to access problems with task and project lists.  Data that is not well-managed has resulted in compromised database security, loss of accountability, version-control issues with the documents, and disorganization of files.  Further, GTU IT technicians share information, track projects, and communicate solely via e-mail.  Miscommunication problems have developed extensively from lost e-mails, failed updates or missed file transfers.  A number of large project deadlines have been missed.  These missed deadlines have resulted in financial loss. The Data representing missed deadlines and the cost analysis is provided below in Figure 1.
In addition, GTU projects a major expansion within the next five years, beginning with the construction of a new downtown campus in September 2010.  Accordingly, IT technicians and support teams will be expected to spend significant time working off-site.  In order for the IT Department to maximize productivity and efficiency, a remote office location is planned.  It is critical that we address our current system’s problems expediently, in order to have the solution in place on or before August 31, 2010.

The following chart (p. 6 fig. 1) illustrates the financial impact of missed project deadlines as a result of communication breakdown from the limitations of GeekWorks 2.1:

IT Department Missed Project Deadline Analysis
January 1, 2009 -  January 31, 2010
Project    Original Deadline    Date Completed    Technician and Support team OT hours    Total Additional Cost

Google Calendar Synchronization    14-Mar-09    15-Mar-09    7    371
IT Division manager reports failure to receive voicemails regarding issue with Daylight Savings Time. IT Division manager was on site at Colorado regional retreat, and cell phone was out of range.
Microsoft Office 2007 Project Rollout    1-Apr-09    15-May-09    63    3276
Project Manager reports missed crucial updates not installed, Incorrect edition of Microsoft Exchange 2007.
YouTube Training Videos – Usability Test    1-Jun-10    13-Jun-10    12    636
Project Manager reports miscommunication between training department deadline and IT department deadlines.  Training Department instructional material was not presented to IT department until June 7.  Training Department did not receive IT Department email regarding new June 1 deadline.
Quickbooks 2009 Update    1-Sep-09    4-Sep-09    26    1378
Additional Accounting Department Support team hours    38    1330
Accounting Team reported request for change in Quickbooks update deadline date via email on August 31.  IT Department was in process of in-field project and missed communication.  Resulted in additional hours spent to install update.  Additional Accounting Department hours required to correct errors due to missed update.

Figure 1.

CRITERIA
The online project management tools were compared by required functionality and characteristics and each product was scored by comparison.
•    Cost of implementation (Purchase, training, installation, maintenance)
•    Ease of use
•    Differentiation from Geekworks 2.1
•    Support Requirements
•    Available Features

REVIEW OF OPTIONS
Project management tools provide the resources for planning, organizing, and managing data, information and people together to bring about the successful completion of specific project goals and objectives.  However, each application reviewed has its own dynamic qualities and/or limitations.  The foremost challenge of these applications is to achieve all of the project goals and objectives while working within project constraints including scope, time, and budget.

ZOHO
Zoho offers a comprehensive suite of award-winning on-line business, productivity & collaboration applications.  Customers use Zoho Applications to run their business processes, manage their information and be more productive while at the office or on the go, without having to worry about expensive or outdated hardware or software.  Primary benefit: clients can customize particular applications to their needs as opposed to paying for a comprehensive plan that includes items they may not otherwise use.

Pros: Data security, control of your data, integration, multilingual, and customer friendly support.
Cons: Individual application download time consuming, not comprehensive for budgetary constraint, and complicated.

BASECAMP
Basecamp is the leading web-based project collaboration tool that allows users to share files, meet deadlines, assign tasks, and centralize feedback.  Primary benefit: Leaders in the market, and have developed a tested and secure system used by many different companies.

Pros: Project development tracking, enabled collaboration, email reminders, visible progress of projects.
Cons: Does not allow you to assign more than one person to a task, no calendar on the dashboard, and plans are expensive.

REVIEW OF OPTIONS (cont.)

SMARTSHEET
Smartsheet Software as a Service (SaaS) provider gives people a fast, easy way to collaborate and get things done. Smartsheet makes individuals who work with others more productive through an innovative, easy-to-use online application.

Pros: Comprehensive package at the most affordable rate that met within budgetary restraints, offers fast upload of files, data encryption, track discussions, allows users to share online with co-workers, clients, contractors, and vendors, and sends email reminders and notifications of updates/changes.
Cons: No deadline alerts.

COMPARISONS
Project Management Applications
Basecamp    Smartsheet    Zoho
Features
Task Management    *    *    *
Calendar    *    *    *
Discussion Board        *
Email Notification        *
Deadline Alerts    *        *
Meeting Alerts    *        *
History Tracking    *    *
Templates    *    *

Cost for license    $600    $325    $1,200
Monthly Fee    0    $50    0
Trial Period    30 Days    14 Days    30 Days

CONCLUSIONS
The results of the usability test concluded that 4 out of 4 users were extremely satisfied with Smartsheet.  Smartsheet allowed the Usability Team to effectively maintain communication during the project. Tasks were completed in a timely manner.  Task management tracking enabled team members to view what portion of the project had been completed and by which team member.  E-mail notifications were sent out to team members whenever changes and updates had been made.  The Discussion Board allowed for team members to upload files and make comments and notations to fellow team members.  File transfers were not limited in file size and assigned to specific sections in order to work on multiple projects if necessary. Calendar and Gantt functions allowed for deadlines to be maintained and e-mail notifications of upcoming deadlines were also provided through Smartsheet.  In addition, Smartsheet costs were well within budget limitations as set forth by GTU.

RECOMMENDATIONS
Based on a thorough examination of the top three project management tools, we recommend Smartsheet.  While Smartsheet is the only project management application that charges a monthly fee, it is also the only one that provides a discussion board and e-mail notifications.  The results of the usability test confirmed that users believe that discussion boards are beneficial to collaboration.
Smartsheet combines spreadsheet-like ease of use with powerful work automation and file sharing – all integrated with data resources.  Its online work management tool takes an easy to use spreadsheet to the next level and is compatible with QuickBooks data import, task management, alerts & reminders, calendar and Gantt views, file sharing and discussion tracking.
Overall Benefits
•    Easy to use spreadsheet-like interface ensures team adoption and easy tracking of work
•    Import of QuickBooks data (with optional filters), including customer and vendor lists, open invoices, estimates, bill and sales orders
•    Track any type of work, including projects, task lists, sales pipelines, IT issue logs, HR checklists, marketing programs, and team goals
•    Collaborate securely on shared work or task lists, attached files and discussion threads
•    Increase accountability with a time-stamped history of all changes and automated alerts & reminders
•    Ensure nothing falls through the cracks with summary reports across all types of work.

REFERENCES
•    Dobrin, Sidney I., Christopher J. Keller, Christian R. Weisser. Technical Communication in the Twenty-First Century. Columbus, OH: Prentice Hall, 2007
•    Dejean, David. “Online Office Apps Get Real: Google Docs vs. ThinkFree vs. Zoho.” Computerworld. 16 July 2008. 14 April 2010. http://www.computerworld.com/s/article/9108799/Online_office_apps_get_real_Google_Docs_vs._ThinkFree_vs._Zoho

•    Wenzel, Elsa. “Alternatives to Microsoft Office.” CNET Reviews. 24 May 2006.  14 April 2010. http://reviews.cnet.com/1990-3524_7-5140428-1.html

•    Basecamp. 14 April 2010. http://basecamphq.com/

•    Smartsheet. 14 April 2010. http://www.smartsheet.com/
•    Zoho. 14 April 2010. http://www.zoho.com/

•    Reynolds, Deanna.  “The Top Ten Benefits of Project Management.” Bright Hub.  28 July 2009.  3 May 2010.

http://www.brighthub.com/office/project-management/articles/2350.aspx

APPENDIX

USABILITY TEST REPORT
FOR GTU IT DEPARTMENT
PROJECT MANAGEMENT TOOL EVALUATION OF:
BASECAMP, ZOHO, SMARTSHEET

Created by Group 1

Valerie Cooper, Jennifer Nguyen, Kathryne Nunley, Osmara Altenhoff
Geek Tech University, IT Department
May 02, 2010

EXECUTIVE SUMMARY

This study was conducted to test the usability success of Basecamp, Zoho, and Smartsheet for possible implementation of these web-based project management applications at GTU IT Department, replacing the current project management system, Geekworks 2.1.  The goal was to measure and identify user satisfaction, ease of task completion, problem areas or inconsistencies with these applications by asking test participants to use the most commonly used features or functions of these web-based applications in relation to projects that the GTU IT staff work on.  Participants completed these tasks at their homes, with the use of their personal computers during their spare time.  Four participants from Geek Tech University IT Department were recruited and screened, based on various computer skill levels and project responsibility.
All participants were required to complete tasks within three days and for the most part, found the web-based applications simple to use, intuitive and agile.  Questionnaires were given to the participants before and after the test were conducted.  Participants were asked to elaborate on their test experience via instant message or email.  Solutions and recommendations leading to a decision as to whether or not these tools will replace Geekworks 2.1 will be determined.

INTRODUCTION
This report describes the plan, execution, and results of conducting the usability test for Basecamp, Zoho and Smartsheet web-based project management applications.

USABILITY TEAM
Test administrators and report writers included Geek Tech University’s IT Help Desk Manager, Valerie Cooper and IT Department partners Osmara Altenhof, Kathryne Nunley, and Jennifer Nguyen.

TEST PARAMETERS
The test was conducted over the course of three days.  Participants were required to complete tasks using specific features of each web-based project management tool.  The test was completed at the participant’s home during their free time and also at their office cubicle.  After completing the instructions on a Mac or PC, participants were asked to complete the post questionnaires and submit them to the GTU IT test administrator, Valerie Cooper immediately thereafter via email.

USABILITY TEST PLAN
Statement of Purpose
The purpose of the usability test was to identify specific problem areas, inconsistencies, issues, strengths and advantages of Basecamp, Zoho and Smartsheet over other existing web-based project management applications.  The users’ reaction and experience with the instructions were measured, observed and examined for the purpose of determining whether or not these applications will be successful in solving the current project management issues and problems involving large scale projects currently plaguing GTU IT Department.

Test Issues
Possible issues with the applications were: unreliability of data security, slow and inefficient file transfer or upload rate, limited storage capacity,  no real-time project tracking,  no conferencing project management feature, lack of tech support, non-intuitive or confusing website design, applications are difficult to learn or use, very expensive software fees.

Test Goals
The test was designed to evaluate the ease of use of the following features:
•    Task management
•    Calendar
•    Discussion board
•    Email notification
•    Deadline and Meeting Alerts
•    History Tracking
•    Templates
Test Environment
Test was performed using a PC, MAC, iPad, iPhone, or Blackberry Devices at the participant’s home or office workstation as outlined below.  Participants completed tasks independently of the test facilitator. Participants were encouraged to think aloud, vocalize and tape record their reactions with an audio or video tape recorder as they used the features of the applications.

Day 1:  Testing was conducted on site, in the office environment of each respective participant.
Day 2:  Testing was conducted in office for Participants 1 and 2, and at remote site Downtown Campus for participants 3 and 4.
Day 3:  Testing was conducted in office for Participants 1 and 2, and at home offices of participants 3 and 4.

Recruitment Methodology
Four test participants were screened and selected based on their level of computer use and experience.  A wide range of computer skills and job responsibilities were required so that the test may reflect the actual user demographic or typical user profile of the GTU IT Department.  Participants recruited had to be employed under Geek Tech University’s IT Department from the main office, as well as at the different field locations.

Every member of the GTU IT staff was contacted via email asking for their voluntary consent to participate in the usability study.

User Profile
Four total participants were selected from the IT department, representative of the members of the department most likely to use the PMT platform:

Participant #1:  Part-time employee, minimal computer experience (limited to email and Internet), employed with GTU for six months.
Participant #2:  Full-time employee, moderate computer experience (some data entry), employed with GTU for two years.
Participant #3:  Full time employee, extensive computer experience (some programming), employed with GTU for five years.
Participant #4:  Salaried management, extensive computer experience (graduate degree IT), employed with GTU for seven years.

Participant Recruitment Plan
An email was sent to the entire GTU IT Department asking for volunteers from different teams of discipline and office locations within the GTU IT Dept.  Also an informal meeting was conducted at the Main Headquarters to recruit participants.  Participating volunteers were given an incentive of $50 gift certificates each towards meals at the GTU Metro Café.

Participant Screening Plan
Each test user had to own a Blackberry, iPad, or iTouch and use both PC and MAC to conduct large-scale projects at GTU IT Dept.  Participants also had to be employed at GTU IT Dept. for at least 3 years.   Each participant had to belong to different teams of discipline at the GTU IT Dept.  and had to be working at the different field locations at GTU IT.

Consent Forms
Participants were asked to sign a consent form via email asking their permission to conduct the test during their free time at their respective homes and during work hours at their cubicles or office.  The consent form explained to the participants that the information they provided will be used to measure effectiveness of the web-based project management tools.  Participant’s identification would be disclosed but would be used only within the GTU IT Department.  The consent form required that the participants complete the test and not withdraw from it.

LIST OF PARTICIPANT TASKS
•    Participants read and signed the consent forms and returned them to GTU IT Dept. via email.
•    The test administrator asked participants to submit questions they had about the test before they began the test.
•    Participants completed a pretest demographic and background info questionnaire.
•    For each PMT, Zoho, Basecamp, and Smartsheet, participants were asked to:
1.    Add a new job/project or a new “to do list” in the PMT
2.    Manage the project in the PMT using the communication or tracking features of the software application and use of message boards or notifications and to change/update the documents.
3.    Upload large and complex project files for database storage.
•    Participants were asked to record their experience using the features and tools either mentally or by taking notes.
•    Participants were asked to record how long they used each application and to describe what the extent of their work was.
•    After testing the features of the applications were completed, participants then had to fill out a post-task questionnaire elaborating on their experience.

METHODS OF EVALUATION
Data Collection Forms and Post Test Questionnaires
Questionnaires regarding ease of use and satisfaction were distributed and collected via email using free-form responses and rating scales.  The time it took to complete the tasks was also measured, from the time the participants began the tasks until the time the tasks were completed.  The participants’ experience was measured against desired usability goals and success requirements, and a tally of errors was kept for inclusion in a frequency report.

TEST RESULTS
Methodology
100% of the participants were able to follow all the tasks assigned to them and completed all tasks as described and listed on the List of Participant Tasks portion of this report.  Each participant spent three days using different features of the PMT tools.

The data collected from the questionnaires and the measures obtained, showed that 100% of participants were able to successfully complete their projects tasks with ease and were a great improvement over Geekworks 2.1.  100% of the participants reported that these PMT’s delivered efficiency, kept track of communication and user satisfaction.

Results

BASECAMP
In testing, 85% of the users found navigation of Basecamp to be time-consuming and clumsy.  Users were unclear how to use features the first time due to the confusing layout of the screen. Simple tasks, such as adding a new document, were difficult to execute as a result of confusing screen layout.  When attempting to add a project or to-do list using a PC, Jaws bugs appeared.  Basecamp also lacked some higher-end collaboration features, such as white-boards.  Basecamp used significant memory, slowing the application on older PCs, and file-sharing required a separate FTP program.  Finally, the writeboard didn’t have a what-you-see-is-what-you-get (WYSIWYG) interface; instead, users had to reference a code sheet for common formatting options.
ZOHO
In testing, 90% of the users described the Zoho’s office applications as too basic and limited. For instance, The Zoho Writer word processor and Zoho Sheet spreadsheet were front ends for outdated versions of OpenOffice.org 2.  Zoho writer allowed import of documents in Word 2003 and earlier, but not in the new Word 2007 format.  Users couldn’t use features like footnotes or endnotes.  The office tools were not fast or powerful enough to deal with large and complex documents, as Zoho bogged down immensely when working with large files.  There were no easy links for help or support.

SMARTSHEET
Regarding Smartsheet, 100% of the users were extremely satisfied with the simplicity, ease of use, elegant design and layout of the application.  Users found few issues when completing different and large-scale job tasks, as the format of Smartsheet was compatible with all operating systems for both PC and MAC, and could be imbedded in existing enterprise platforms.  This allowed users to create tasks and documents with the use of the most current
TEST RESULTS (cont.)
versions of MS Office, or other office applications.  The applications were very user-friendly, fast and efficient.  Users were able to pass information and documents among employees and teams very clearly and kept projects in one manageable place.  There were no major bog-downs during file transfers and uploading.  Alerts existed to notify project managers when changes were made to a project, or when the job was completed.  There were message boards for communication.  Changes could be seen in real time.  Documents were easy to locate. Another feature which our users were very happy with was that Smartsheet is Ajax-based and built on commercial-grade open source tools to ensure scalability and reliability.  Security features were also impressive, offering privacy settings, access controls, SSL encrypted user authentications and data encryption.
Conclusions
Based on the usability test, Zoho and Basecamp applications offered the most features, but users were overwhelmed with the complexity of applications.  In addition, the cost of implementation would exceed the GTU IT budget.  A simpler and more efficient project management tool is better suited to the needs of the GTU IT department.
Of the Project Management Tools tested, Smartsheet Project Management Tool proved to be the best solution for the GTU IT department.  In addition to ease of use, reliability, and efficiency, Smartsheet is also the most cost-effective solution.  Project management is complex, but the simplicity and efficiency offered by Smartsheet is key.  In addition, Smartsheet provides remote accessibility, secure data storage and fast downloading, while also serving as an excellent communication standard.  In conclusion, we are confident that productivity will be increased with the implementation of Smartsheet as a replacement for Geekworks 2.1.

APPENDICES
Copies of the Consent Form, Data sheets, Screening questionnaires, Pre-test and Post-test questionnaires, and participant responses may be obtained by sending an email to vrcooper@asu.edu or by contacting the GTU IT Department at: Geek Tech University, 135 Main Street, IT Bldg. Room 4, San Francisco CA 94114.

 

D#14, HW#3 – Memo Update April 21, 2010

Filed under: Deadline #14,Projects — jennifermai73 @ 6:45 am

TO:  Dr. Rodrigo
FROM:  Osmara Altenhof, Valerie Cooper, Jennifer Nguyen, Kathryne Nunley, Marsha Wasson, Anthony Corder

RE:  Proposal Update – Online Project Management Applications

Below, please find an update to our proposal regarding evaluation of online project management software applications.  Time and Action project deadlines are updated as follows:

Task 1: Investigate Problem

1.      Complete Screen for three largest missed deadline projects complete April 23.

2.     Complete  Begin analysis of missed deadline projects April 24.

3.     Complete  Complete missed project analysis April 25.

Task 2: Identify Options

1.      In Process  Begin feature analysis of available Project Management applications.

2.       In Process Identify three applications for further research by April 27.

Task 3: Identify Comparison Criteria

In Process, as above.

Task 4: Research Options

1.     Complete  Identify associates for in-field usability testing by April 25.

2.      In Process Prepare protocol for in-field usability testing by April 25.

3.      Complete Acquire trial software for usability testing of three applications identified, by April 26.

4.      Scheduled May 1 Conduct 7-day usability testing in field.  Complete testing May 4.

Task 5:  Evaluate Options

On Schedule  Analyze results of usability testing.  Compile and complete final report for Board by May 7.

Task 6:  Prepare Recommendation Report

We look forward to presenting the results of our analysis and testing to the Board, as scheduled, on May 8.

 

D#14, HW#2 April 21, 2010

Filed under: Deadline #14 — jennifermai73 @ 6:42 am

Presentations (pg. 391)

  • Analyzing Your Audience (pg. 392)
  • Gathering Information (pg. 392)
  • Selecting Visuals (pg. 553)
  • Using Visuals (pg. 395)
  • Delivering a Presentation (pg. 398)
 

D#13, HW#3 April 15, 2010

Filed under: Deadline #13 — jennifermai73 @ 8:02 am

The first thing I changed on my blog was the theme. I choose one that was easy to read and wasn’t too distracting for the audience.  I then created an “About” me page that provide readers with the purpose of the blog.  The widgets that I added were “Comments” and “Categories.”  For me personally, I had a hard time finding comments left by readers.  The link is so small and it’s located at the bottom of the post.  So, I added a widget to the side of my blog that gave readers easy access to comments.  I also added a dropdown Categories bar so readers could find information easier.  Instead of having to search through all the posts, readers can now locate posts by category.  Also, all posts are now organized within 14 categories.  In addition to these changes, I also added a search bar and a subscription sign up link.  The search bar allows readers to type in exactly what it is they’re looking for and the sign up link allows user to subscribe to my blog.

 

D#12, HW# 2 – Reflection April 15, 2010

Filed under: Deadline #12,Reflection — jennifermai73 @ 7:52 am

1.  What were the steps you took to complete the project? How might you change your process if you were to complete the project again? What steps do you think you will take for your next project?

Completing the proposal project involved many steps.  The first thing that was done was the selection of the project manager.  Luckily for our group, Osmara stepped up to the plate and volunteered!  Before even attempting the project, Osmara suggested that we all respond to e-mails within 24 hours, just so we could keep on top of things.  We all thought it was a great idea.

The next step was assembling the Team Charter.  With input from the entire group (sans the two that we never heard from), Osmara constructed the Team Charter.  After the charter was in place we got to work on the tasks and schedules.  This was easy because everyone was so willing to contribute.

With the charter, tasks, and schedule out of the way, Valerie and I started soliciting information from the group regarding possible problems and solutions.  Once everyone e-mailed in their suggestions, Valerie and I got to work composing the proposal.

Kathi then took our draft and made sure all the necessary elements were included as well as revised it.  She completed the final proposal.

Personally, as a group project, I think the steps we took worked really well.  Everyone responded in a timely manner and everyone contributed, with the exception of the two we never heard from.  Luckily since we never heard from them, we didn’t assign any tasks to them, so no elements were missing or incomplete.  For my next group project I think I would definitely follow Osmara’s lead.  She took the initiative to sign the group up for Smartsheet which made collaborating really easy!

2.  What are you most proud of in this project? Why are you proud? What are you most concerned with in this project? How did you try to address that concern before finally submitting your project? If you had more time, how might you further work on that concern?

For this project I’m most proud of how well our group worked together.  I’ve been in groups before where I ended up doing all the work while everyone else got credit for it.  This group was just so easy to work with and I don’t feel as if any one member contributed more or less than another.  To be honest, I’m not really concerned with much on this project.  I think the four of us were able to come up with a really good proposal and I’m exciting to start researching the project management applications.

3.  In terms of learning about composing, what did you specifically work on to improve during this project? Do you feel you succeeded in improving your composing processes or skills? What composing processes or skills will you work on during your next project?

In terms of learning about composing, I really focused on the outline of the proposal and including all the necessary elements.  While it was in memo format, there were many other things that need to be included such as tasks and schedule.  I feel like we did a good job including all the necessary elements and providing sufficient detail.  I will definitely use the outline we created for any other proposal projects.

4.  What course outcomes did you work towards during this project? Do you feel you achieved them? How do you know? What evidence does either your process or product for this current writing provide towards demonstrating your achievement of a course outcome? What outcomes do you think you will work on in your next project?

In terms of course outcomes, I really worked towards understanding the collaborative and social aspects of research and writing processes.  Even though I’ve yet to meet the members of my group, I feel as if I somewhat already know them.  Working with them and bouncing ideas off of each other really helped organize my thoughts and enabled me to achieve clarity in my writing.  The process of e-mailing back and forth and checking in with each other demonstrates the collaborative aspect of our project.  For the next project, I’d like to work on develop flexible strategies for generating, revising, editing, and proof-reading.

 

D#12, HW#1 – Project Proposal April 15, 2010

Filed under: Deadline #12,Projects — jennifermai73 @ 7:50 am

A Proposal to Evaluate Online Project Management Applications

For:

Dr. Shelley Rodrigo, CIO

Geek Tech University

IT Department

Submitted by:

Osmara Altenhof, CSO

Valerie Cooper, Help Desk Manager

Kathryne Nunley, CTO

Jennifer Nguyen, Director, E-Commerce

April 23, 2010

MEMO

Date: April 24, 2010

To: Dr. Shelley Rodrigo, CIO, GTU IT Dept.

From: TWC301 Group 1, IT Dept.

Subject: Proposal for Evaluating Online Project Management Applications

Purpose

The purpose of this proposal is to request authorization to evaluate online project management applications in order to determine their usefulness in assisting with the completion of large-scale projects at the GTU IT Department.

Summary

Currently, the IT personnel at Geek Tech University facilitate multidimensional operational tasks including file sharing, data management, project tracking and communications solely via use of email. Concerns have escalated over this system, as email file transmissions can be slow, inconsistent, and are not guaranteed.  Lost or unread emails have resulted in delayed or unmet project deadlines. The GTU IT staff offer consideration of an online project management system as the most effective solution for our expanding project management needs.  We are confident that a centralized, web-based communications and information system will result in significantly improved compliance with project deadlines.

Upon approval of this proposal, we will begin a comprehensive evaluation of various project management applications to assess their respective benefits.  After establishing accounts with at least three online project management applications, we will test the various options of each to determine their respective benefits for project management.

To perform this research and to present a report on our findings, we estimate that it will require 40 hours of our time over the next month, at the total cost of $600 in wages. The proposed research team consists of four technicians: Osmara Altenhof, Valerie Cooper, Kathryne Nunley, and Jennifer Nguyen.  Upon acceptance of this proposal, research will begin immediately, followed by a progress report on May 1, 2010.  A final report on May 8, 2010 will include the details of our research, and a recommendation for the web-based productivity tool that would best serve the GTU IT Department.

Introduction

The GTU IT Department has grown threefold over the last 5 years.  It is one of the largest university-based IT support teams in the US, employing over 300 employees nationwide.  The financial impact of our exponential growth has been very positive, but has presented the IT Department with operational challenges.  Under the antiquated project management system (GeekWorks 2.1) in place since 2008, we are unable to effectively manage and support large-scale projects within the department.  Our entire staff, especially those in remote locations, has expressed valid concerns with communication and task management relative to the current system.

As a result, The GTU IT Department has suffered a decline in productivity due to access problems with task and project lists. Data that is not well-managed has resulted in compromised database security, loss of accountability, version-control issues with the documents, and disorganization of files. Further, GTU IT technicians share information, track projects, and communicate solely via e-mail.  Miscommunication problems have developed extensively from lost e-mails, failed updates or missed file transfers.  A number of large project deadlines have been missed. These missed deadlines have resulted in financial loss, the extent of which will be analyzed in our proposed research report.

In addition, GTU projects a major expansion within the next five years, beginning with the construction of a new downtown campus in September 2010.  Accordingly, IT technicians and support teams will be expected to spend significant time working off-site.  In order for the IT Department to maximize productivity and efficiency, a remote office location is planned.  It is critical that we address our current system’s problems expediently, in order to have the solution in place on or before August 31, 2010.

We propose to study various online project management tools that will adequately support our team.  We will investigate features including, but not limited to, code-encrypted file sharing, web-based mass storage and access, email notifications, deadline and meeting alerts, a history-tracker for changes made to documents and projects, user-friendly templates, and calendar functions.

Proposed Tasks

Upon approval, we will initiate the following tasks to determine the best solution for managing large projects.

  1. Identify available project management application options
  2. Identify the main criteria by which we will compare online project management applications.
    1. Cost to implement (purchase, training, installation)
    2. Ease of use
    3. Features
      1. i.     Task management
      2. ii.     Calendar
      3. iii.     Discussion board
      4. iv.     Email notification
      5. v.     Deadline and Meeting Alerts
      6. vi.     History Tracking
      7. vii.     Templates
      8. Conduct research for selected online project management applications.
      9. Evaluate options based on the identified criteria in Task #3.
      10. Prepare a recommendation report, with presentation to the Board on or before May 8, 2010.

Schedule

Following is a schedule of the tasks we will complete for this project:

Task 1: Investigate Problem

  1. Screen for three largest missed deadline projects complete by April 23, 2010.
  2. Begin analysis of missed deadline projects by April 24, 2010.
  3. Complete missed project analysis by April 25, 2010.

Task 2: Identify Options

  1. Begin feature analysis of available Project Management applications.
  2. Identify three applications for further research by April 27, 2010.

Task 3: Identify Comparison Criteria

Complete, as above.

Task 4: Research Options

  1. Identify associates for in-field usability testing by April 25, 2010.
  2. Prepare protocol for in-field usability testing by April 25, 2010.
  3. Acquire trial software for usability testing of three applications identified, by April 26, 2010.
  4. Conduct 7-day usability testing in field.  Complete testing by May 4, 2010.

Task 5:  Evaluate Options

Analyze results of usability testing.  Compile and complete final report for Board by May 7, 2010.

Task 6:  Prepare Recommendation Report

Presentation to Board on May 8, 2010.

Experience

We bring over 40 years of combined experience as technicians at GTU to the project:

  • Osmara Altenhof, CSO, 17 years experience as Graphic Design and Support, Regional Office.
  • Valerie Cooper, Help Desk Manager at GTU, 8 yrs. Experience as Software Support Specialist at GTU, Master of Science in Information, 2000 Polytechnic University of The Eastern Sea, Member of the Arizona Human and Computer Interaction Chapter.
  • Kathryne Nunley, CTO, 7 years experience directing team of 7 regional IT managers at GTU, Masters of Science in Technology, 1999 Polytechnic University of the High Mountains.  IT Department head, Macrosoft 1999-2001.
  • Jennifer Nguyen, Director of Electronic Commerce, 9 years experience in IT senior management, two of which have been at GTU. Certified in Organizational Leadership and Human Resources.  Associate’s degree in Organizational Management from Chandler-Gilbert Community College.

Budget

Following is an itemized budget for out proposed research.

Name Hours Hourly Rate Cost
Osmara Altenhof 10 $15 $150
Valerie Cooper 10 $15 $150
Kathryne Nunley 10 $15 $150
Jennifer Nguyen 10 $15 $150

Total:                                       $600

 

D#10, HW#2 – Team Writing Chapter 8 April 1, 2010

Filed under: Deadline #10,Team writing — jennifermai73 @ 11:23 pm

HTW has a very useful section titled Collaborative Writing that addresses Conflicts on page 74.  Listening on page 307 is also helpful because it talks about the differences between hearing (passive) and listening (active).  Reading both of these sections will help in establishing effective communication between team members.

 

D# 10, HW# 4 – Project 3 Reflection April 1, 2010

Filed under: Deadline #10,Reflection — jennifermai73 @ 11:03 pm

What were the steps you took to complete the entire project #3? How might you change your process if you were to complete the project again?

Before started Project #3, I read and reread Chapter 11 in Technical Communication in the Twenty-First Century. I wanted to be sure I understood what it was that was being asked of me.  I was a little confused at first, thinking that I was supposed to created a usability test on Picasa itself, as opposed to my instruction documents.  Once I figured that it, it got so much easier!

The first step I took was the draft posted in the discussion board.  The draft was helpful because I really got me thinking about what I wanted my report to look like and what questions I wanted to answer.

The second step was to create a participant screening plan and “recruit” participants. Using freeonlinesurveys.com made this process a lot easier for me.  That website also helped me create my posttest questionnaire.

The third step I took was to review the instructor’s comments as well as the participants’ comments.  I then started to construct my usability report following the guidelines provided.

What steps do you think you will take for your next project?

Reading the chapters are a good stepping point for starting any project.  If information is not available, I would then research information online.

What are you most proud of in this project? Why are you proud? What are you most concerned with in this project? How did you try to address that concern before finally submitting your project? If you had more time, how might you further work on that concern?

I’m really proud of how the entire project turned out.  I admit at first I was really stressed about how to conduct an online usability report.  I wasn’t sure about making up information like where the testing was taking place and so on.  My biggest achievement was learning how to include a link in an email that contains what I want it to say versus the link itself.  I never knew how to do that before!  I was most concerned about how professional the report looked.  I tried to use bold type fonts and heading to make it look more professional.  I was also concerned with the Table of Contents.  Microsoft Word has an option for creating a Table of Contents for you, but I couldn’t figure out how to use it!  If I had more time I would have researched it using the Help Index.  The Table of Contents that I created had ellipses that were not centered making the numbers uneven.

In terms of learning about composing, what did you specifically work on to improve during this project? Do you feel you succeeded in improving your composing processes or skills? What composing processes or skills will you work on during your next project?

Again, I specifically worked on making the project look professional and not just thrown together.  I wanted it to look like an actual technical document and not just one that was typed up.  I definitely think I improved on my composing skills.  I know how to use Microsoft Word a little better now too, which will help me continue to make professional documents.  On my next project, I want to work more on using borders and images.

What course outcomes did you work towards during this project? Do you feel you achieved them? How do you know? What evidence does either your process or product for this current writing provide towards demonstrating your achievement of a course outcome? What outcomes do you think you will work on in your next project?

For this project, I was able to identify, articulate, and focus on a defined purpose; create a usability test that provides insight into user problems, concerns, and preferences.  I also worked towards using appropriate technologies to manage data and information collected.  The freeonlinesurveys.com website helped me achieve this.

 

D# 10, HW# 3 – Revision of Written Documents April 1, 2010

Filed under: Deadline #10,Projects — jennifermai73 @ 11:02 pm

Revised-How To Create a CD

Revised-How to Create an Album

Revised-How To Email Photos

Revised-How to Import Photos

 

 
Follow

Get every new post delivered to your Inbox.