CS250 as a Project (status report)

     As we enter our fourth month in IT Project Management, let us take a quick look at how things are going so far (from a project perspective).  We have learned some paramount information concerning project planning, communication, dealing with different personalities, keeping motivated, and utilizing teamwork toward projects and project management.

     The group projects for actual clients have displayed real-world problems which project managers have had to overcome.  This is a great teaching tool, in that it shows no matter how much you learn in a classroom environment, it means nothing until applied to real-life situations and application.  While everyone thinks that a project will not fail, because we follow all the rules learned in the classroom, they are quickly learning how easy it is for a project to fail if not constantly maintained.  Communication has been the key to knowing where the projects are, and what still needs to get done.

During the progress review, how might a project manager assess the contribution of each member of the project team?

     A project manager can assess the contribution of each member of the project team based on the type of information each member provides to the review.  If the member is detailed in their progress report, it is an indication that the member has put a lot into the project.  Information provided such as percentage accomplished, milestones reached, graphic descriptions of work accomplished, and pitfalls overcome, suggestions, collaborations and tangible results are strong indicators that that member has been contributing a lot to the project.

     On the other side of the spectrum, if the member has very little information to provide, or provides numerous excuses why something is not done, it is a good indication that the member has contributed little to the project. 

     Good communication is also a good indicator for project managers to know a member’s contributions.  Maintaining good records, such as weekly reports, helps the project manager see what a member has accomplished each week.  Also, constant communication between the project manager and the project members keeps the project manager apprised of where each member is with the project.  A member who does not maintain regular communications, or maintain weekly reports, conveys a message to the project manager that they are not contributing to the project.  Even though they might be getting a lot done, without good communication, the project manager does not know.

Why is user-centered development critical to successful systems development projects?

     User-centered development is critical because it is the end-user that is going to be using the product.  In the world of technology the consumer user outnumbers the professional user by a substantial margin.  It is essential to listen to the end-user when developing systems. If the system is too complicated and difficult to understand and use, then the project has failed to meet its goal. 

     In addition, when developing a specific system, it is the end-user that knows what they want the system to be able to do.  An engineer or software developer needs to know what exactly the end-user desires in the capabilities of the system.  A programmer can speculate what he thinks the end-user will need the software to do, but without getting that information from the user, the project will fall short. 

     Today’s technology is much too dynamic compared to twenty-five years ago.  In the late 1980’s – early 1990’s, developers put together software packages and users bought them and used them.  Now, with open-source and mobile applications, it is much simpler for the user to find an application that suite their particular needs.  If they cannot find it, they can have one built to their specifications relatively easy.

     The more end-users involved during development ensures that all required operations will be included in the final project.  This is definitely an environment where a “bottom-up” methodology is the better way to go. 

Evaluating My Own Presentation

In my presentation, I was innovative in coming up with a desired solution to the scenario given about creating catalogs for an online clothing company.  My introduction could have been better, but my overall structure flowed with the desired information and how I wanted to present it.  I also need some improvement with timing, which could be integrated into my notes for presentation. I could have been strengthened by a couple of PowerPoint slides, but I wanted to refrain from using any type of technological crutch for this presentation.  Overall, I feel I got my message across to the audience.

Tips for Presenters of Presentations

Here are a few tips for presenters to help when preparing for and giving presentations.

• Ensure you know the material being presented.
• Practice your presentation prior to the actual presentation.
• Have a structure to the presentation, intro, body, & conclusion.
• Interact with the audience.
• Keep the audience's attention, through humor, stories, fluctuation in voice level, etc..
• Be confident during the presentation.
• Keep good eye contact with the audience.
• Ask questions and get audience participation occasionally.