Get Blog Updates!

Enter your email address:

Delivered by FeedBurner

Featured Products

How to Effectively Build A Project Schedule
How to Effectively Build A Project Schedule
$29.00

Currently Reading

Tactical PM Tips Newsletter: Project Management and Twitter

Print E-mail
Written by Dr. Andrew Makar   
Tuesday, 18 August 2009 08:33
AddThis Social Bookmark Button
In this Tactical Tips issue, Tactical Project Management presents:

• Project Management and Twitter
• PM Tip: Get your latest PM news using Google Reader
• Recommended Reading

News You Can Use

Project Management and Twitter

My search for social media applications for project management continues to identify additional tools that project managers can use to enhance their learning and improve collaboration with a worldwide community of practice. If you study social media, you can't go too far before learning about Twitter. I written about the topic and its application to project management learning is a useful one.

I don't use Twitter to learn about where my friends are at, what they are doing, or their latest witty comment or outlook on life. Facebook is a much better application to keep in touch with friends and keep your personal life...well...personal. I DO use Twitter to learn about what other project managers are doing, what they are reading, and asking questions through my project management network. Twitter operates on a simply concept of distribution 140 word characters to everyone who is following you.

As a guideline, I only follow project managers or people who produce useful project management content. As a result, anytime someone I'm following sends a "tweet", I quickly get a 140 character description of the project management snippet. If I want to learn more, there is usually a URL included. This approach quite simply saves time and when someone I value sends a tweet, I'm more likely to look at it.

If you want to jumpstart your Twitter and Project Management follow list, I recommend you follow these project management practitioners:

Dave Garrett @DaveG253
Naomi Caietti @califgirl232
Elizabeth Harrin @Pm4girls
Elyse Nielsen @anticlue
Cornelius Ficht @corneliusficht
Andy Makar @andymakar

(yes I had to include my own plug...)

For a quick overview on Twitter for business checkout:
A quick Twitter guide and glossary for business users

Upcoming Mind Jet Mind Manager Webinar

Please mark your calendars for September 10th for an upcoming webinar on mind mapping and project management with MindJet Mind Manager. I've been asked to co-present so I look forward to seeing you virtually on the seminar! It is a no-cost webinar that will highlight mind mapping and project management in action. Stay tuned for more details. Once the registration URL is live, I'll let you know.

Tactical Project Management Tip

Get your latest PM news using Google Reader

If you want to keep up with the latest project management news in our industry, give Google Reader a try. Google Reader is a Really Simply Syndication (RSS) reader that simply aggregates the latest news feeds into one easy to read view. If you find a favorite project management website like (ahem) http://www.tacticalprojectmanagement.com, you can add its RSS feed to your Google Reader. Instead of visiting multiple websites to get your latest project management news, articles or tips, I just use Google Reader to get a preview of all the relevant articles.

You can access Google Reader by visiting http://reader.google.com
Below are just a few of the RSS feeds that I recommend. Just copy the RSS link into your Google Reader.

Hearding Cats http://feeds.feedburner.com/typepad/HerdingCats

Gantthead http://www.gantthead.com/RSS/gantthead.xml

Projects@Work http://www.projectsatwork.com/RSS/projectsatwork.xml

Tactical Project Management Blog http://www.tacticalprojectmanagement.com/tactical-tips/feed/rss.html

Did I mention that Google Reader looks great on the iPhone? The majority of my reading is done via the iPhone while waiting in-line or during those "deadspots" in meetings. (I'll let you define your own deadspots as some poorly run meetings can consist entirely of deadspots).

Recommended Reading: One Page Project Manager

The One Page Project Manager is an interesting premise - What if you could communicate and manage an entire project using one sheet of paper? The author, Clark Campbell, provides a template and the mechanics of adding milestones, issues, risks to provide an overall summary of the project. The data tracks all the major aspects of a project on a simple page. We often manage complex projects and the ability to clearly communicate key details, engage with stakeholders, and successfully track progress is a useful feature condensed into a single sheet of paper.

Mr. Campbell offers two books using this approach - one for general project management and one for IT project Management. If you're looking for a simple way to reference the latest project status and simplify communication, check out the book. I enjoyed it.

Check 'em out at:

  1. The One-Page Project Manager: Communicate and Manage Any Project With a Single Sheet of Paper
  2. The One Page Project Manager for IT Projects: Communicate and Manage Any Project With A Single Sheet of Paper

Hope the rest of your week is a good one!

Thanks!

Andy
This e-mail address is being protected from spambots. You need JavaScript enabled to view it
http://www.twitter.com/andymakar
http://www.tacticalprojectmanagement.com

MS Project Tutorial - Learn how to EFFECTIVELY develop a Project Schedule

 

Add a comment
 

MS Project Tutorial: Earned Value Management Checklist

Print E-mail
Written by Dr. Andrew Makar   
Monday, 17 August 2009 16:32
AddThis Social Bookmark Button

Is your Microsoft Project schedule ready for earned value metrics?  I recently wrote MS Project tutorial for Tech Republic that identifies 8 checklist items before you start calculating earned value management with Microsoft Project.  Calculating earned value metrics such as SPI (schedule performance index) or CPI (cost performance index) is easy in Microsoft Project, but the project schedule needs to be setup correctly.  If your project schedule has poorly defined tasks, missing resources, or a missing baseline, you won't be able to calculate meaningful earned value management metrics.

Check out the article at: Confirm your Microsoft Project Schedule is ready for EVM

 

Add a comment
 

Stop with the Lessons Learned

Print E-mail
Written by Dr. Andrew Makar   
Monday, 17 August 2009 15:51
AddThis Social Bookmark Button
Project teams should simply stop conducting post-mortems and stop wasting time facilitating lessons learned workshops. When I first heard these words I thought it would’ve been considered blasphemy to the PMBOK editorial staff. Undoubtedly the Project Management Institute would revoke PMP certifications on the spot if they found the speaker (ahem…culprit) uttering such nonsense. To think I heard these words of advice at a PMI Seminars World conference was even more surprising. With my curiosity peaked, I listened a little bit more.
I was attending a seminar course sponsored by the PMI Seminar’s World on practical advice for successful project management. I was interested in taking the course to compare notes and learn from other project managers and their real-life battle stories implementing project in the trenches.

The speaker started one of his lecture topics asking the audience how many project managers conducted post-mortems or lessons learned workshops during the project close phase. Like all process conscious PMP-certified project managers, 99 percent of the class raised their hands. The speaker then asked how many project managers review a lessons-learned repository prior to initiating their next project to incorporate best practices. A large portion of the raised hands quickly fell amongst stifled snickers and humbled smiles. We all knew we’re supposed to review lessons learned prior to a project since we documented them from the previous project.
We thought this was a gentle reminder to incorporate lessons learned into project initiation when the speaker asked how many of the project managers go in front of the project’s sponsors and indicate how the lessons learned from previous projects will be applied to the current project. There wasn’t a single hand raised in the room.

The speaker continued with several simple examples on how to conduct an effective lessons learned workshop. Throughout the seminar, the audience learned a lot of practical advice however the importance of linking lessons learned with project initiation, promoting knowledge management and presenting the lessons learned to the project sponsors was a key takeaway.

Ensuring lessons learned are incorporated within the project initiation phase can be implemented by involving project stakeholders and the project management office. A project kick-off presentation can be used to highlight the lessons learned with the business stakeholders. If the PMO uses tollgates, the project initiation kick-off presentation can be audited for reusable lessons learned as the project approaches its initial tollgate. However, ensuring the lessons learned are applied to the current project and the project stakeholders understand how they will be applied is more important. Project managers also stake their professional reputation if the issues from previous lessons learned occur again. This review and commitment to improve is a realistic approach to improving PM maturity without completing another checklist.

The speaker also recommended conducting the lessons learned workshop within a week of the end of the project to ensure the feedback isn’t lost as team members move to the next project. If the project has been a troubled project, project team members will quickly flock to the next project or the next available source of refuge. Conducting the lessons learned session for a troubled project can be difficult as team members work to put the poor experiences past them. Conducting a session within one week of the project end date minimizes the loss of feedback.

It was refreshing attending a PM course that was grounded in theory yet proven in practice. If you’re not going to review the lessons learned from a post-mortem prior to starting a project and incorporate them into the next project, stop conducting lessons learned workshops and wasting time with post-mortems. Without reuse or direct application of the lessons learned, the results of the lessons learned session meet the same fate as the majority of your system documentation. They fall into obscurity archived on a file server only to be reviewed when the network drive is out of space.

The speaker was Neal Whitten--he is a frequent speaker at conferences, seminars, workshops and special events serving private companies, institutions and public organizations. His key course is "No-Nonsense Advice for Successful Projects", and his two most recent books focus on no-nonsense advice and straight-forward talk on practical project management implementation. Readers can find Mr. Whitten’s books and seminar offerings at http://www.nealwhittengroup.com.

Add a comment
 

Project deployment: Avoid being Lost in Transition

Print E-mail
Written by Dr. Andrew Makar   
Monday, 17 August 2009 15:46
AddThis Social Bookmark Button

Have you ever struggled with supporting a newly deployed application while managing subsequent releases? Enterprise projects and programs often have multiple releases to various countries and business units. Project teams run the risk of becoming lost in transition when the initial release is not properly transitioned to an operation support model.

In this scenario, the project team continues to work on the next release while struggling with the production support role. The project team ineffectively juggles operational activities with key project deliverables. Without defined operational roles and responsibilities, project teams endanger future releases as well suffer from role confusion.

This article provides several recommendations to avoid becoming “lost in transition”.
During a recent project, an IT organization was implementing a new financial accounting package over six months with two planned releases. his scenario could be encountered within any range of organizations, from an online casino to a construction management corporation.The first release was implemented to 1/3 of the company and the second release was scoped for the remainder of the company. The first launch was a challenged launch as the system experienced production support issues and the business partners were not comfortable that the system was stable enough to support the remaining 2/3 of the organization. As the team approached the launch decision for the second release, the business partners and the project team decided to postpone the launch for 30 days.


The key reason wasn’t the technical capabilities of the product or outstanding minor production support incidents. During the launch decision meeting, the business partners raised concerns about the instability of the application and the lack of sufficient operational support. After further investigation, the instability was a perception rather than an actual reality. The application response time was acceptable and the Web server never went down. The system functioned as designed however; the perceived instability was directly related to the lack of response from the support team.The key reason contributing to the lack of response was that production support was provided by the existing project team. The project team never transitioned operational support to another team or an individual.

The project team continued to respond to operational issues while trying to deliver the next release of the software implementation. The project issues log was a compilation of operational issues and release specific issues. The project also relied on multiple vendors to manage integration with the software product. The various vendors raised operations issues to multiple points of contact. The end result was confusion. Once the decision to defer the launch was finalized, the project team members became defensive and a bit demoralized by the lack of ownership and the lack of recognition for long hours spent delivering the second phase and production support.

This entire “lost in transition” scenario could have been avoided if the project team included operations support planning and transition early on in the project planning and schedule development. The project team solved the problem by implementing the following six simple steps to improve application governance and improve operational support.

1. Identify support resources for the applicationEven in resource constrained organizations, it is important to have an individual resource or team responsible for production support. Depending on the volume, the role may be shared or dedicated to production support and application management.

2. Establish an operations status meeting with business partners and IT stakeholdersAn operations status meeting is similar to a project status meeting except the focus is on the operations of the IT application and the results being delivered to the business. The operations status meeting includes business partners and IT management to jointly review the health and performance of the application.

3. Establish a production issues and incidents meeting with business subject matter experts and the technical team
By establishing a separate meeting to review production issues and incidents, the project team can focus on issues relevant to the next release while the operations team focuses on immediate support issues. Failing to separate production issues from project issues will only drain the project team from their intended goals and objectives. The end user becomes confused as they struggle with identifying a single point of contact for assistance.

4. Establish a change control board to manage ongoing change in the operational environment
Change management is an ongoing operational process as well as a project management process area. Business needs will change and new reports, fields, interfaces and customizations will be needed. Some of these enhancements can be bundled with a future software release and others will be made off-cycle based on the request’s severity.By establishing a change control board, the business customer will have a method to request changes to the application without deterring the project team from their intended goal. The changes introduced to the change control board should also be vetted and reviewed with the project team to ensure there are no impacts or conflicts.

5. Communicate the governance model to project stakeholders
Once the participants are identified for each of the key operational meetings, the operations governance model should be communicated and reviewed by business and IT stakeholders. By presenting a solution on how issues, changes and operational status will be reviewed, the business partners will have greater confidence in the IT manager’s role in delivering services and supporting the business.

6. Provide knowledge transfer between project team and support team.Another key to a successful operations process is the knowledge transfer provided by the project team to the operational support team. In some cases, project team members will become operational support and in other cases, new operations support teams will be hired independent of the project. The project schedule should include transition documentation tasks to communicate the processes and procedures required to support the application. The processes documentation can include batch schedules, help desk coordination, escalation contacts, known problems and solutions, and disaster recovery procedures.

Readers may be surprised that even a seasoned project team could get “lost in transition”, but it often happens when projects are faced with insufficient resources and short timelines. The triple constraint of scope, time and resources is adjusted when the time parameter is fixed. Scope and resource constraints will adjust and unfortunately operations support maybe de-scoped and poorly implemented. By following these six steps, project teams can ensure a better separation of duties between ongoing operations and future application delivery.

Authors Note: I wrote this article in September 2008 and originally published it on www.gantthead.comI highly recommend gantthead.com for more additional project management resources. 

Add a comment
 

Mind Map Your Job Interview

Print E-mail
Written by Dr. Andrew Makar   
Monday, 17 August 2009 15:38
AddThis Social Bookmark Button

Interviewing for a high-visibility project internally or a new opportunity outside your company can be nerve-wracking. Using mind-mapping techniques to organize your introduction, elevator speech, key experiences and follow-up questions can help you prepare. Here’s a primer for a typical 30-minute interview.

As project managers, we are often looking for the next available project as the current project closes. Regardless if you’re seeking a new position in the market or the next internal high-visibility project, interviews are a common occurrence in the project management domain. Understandably, senior management and perspective employers want to “audition” and approve the project manager before handing over a multi-million dollar program or project.

Preparing for an interview is a nerve-wracking experience. You know everything you say and do is being evaluated. You are concerned about your appearance, making a good first impression, responding with articulate answers, and hoping you’re providing sufficient detail without overwhelming the hiring manager about past project nuances, acronyms and tidbits. The amount of preparation may vary depending on your risk tolerance, interview skills and the job importance. Some project managers can simply walk into an interview with little or no preparation and describe their qualifications like a recap of last night’s American Idol performance. Others spend a few hours updating their resumes, making notes, and even rehearsing for the interview. I’ve always been a fan of preparation, although usually five minutes before the interview, I’m reviewing my resume and comments frantically thinking I forgot something. After all, I wanted to be prepared for any possible question with the perfect answer.

Jim Hoover, one of my former managers, helped reduce my pre-interview jitters by describing an approach for any interview. I applied his approach and, ever since, interviewing has been as easy as holding a casual conversation. I also applied a mind map format to his approach and now I can quickly pull out a single sheet of paper, perform a quick review of key thoughts and experiences, and relax knowing I’m prepared for the interview.

The Approach
The approach is designed for a 30-minute interview, although it can be applied to longer interview sessions. It is important to remember the key points you want to communicate in addition to answering the interview questions.

Introduction (5 minutes)
The introduction is a lot more than a greeting while looking the hiring manager in the eye with a firm handshake. Onsite office interviews are often scheduled in-between meetings during a manager’s free time. Often, the interviewer may be a few minutes late or generally unprepared to start the interview. This is an excellent opportunity for you to direct the discussion with a brief summary of your background.

During the introduction, you want to recite your prepared “elevator speech” that summarizes your background and qualifications. For example, “I’m a PMP-certified program manager with over 12 years experience implementing large scale ERP implementations in human resource and finance functions. Over the past three years, I’ve established PMOs for enterprise programs in both software development and infrastructure management organizations.”
I’ve used this approach several times when the interviewers struggled at initiating the interview questions. It is an effective approach to demonstrate initiative and confidence in the interview.

Position Overview (5-10 minutes)
The next five to ten minutes the interviewers will typically provide a brief overview of the project. Depending on the dialogue, the interviewers may go into additional detail before asking key questions. You want to apply your listening skills because the next series of questions will try to determine how well your background fits the project.

For each of the next three questions, you’ll want to apply the STAR formula: Situation, Task, Action, Result. For every interview question, respond with a description of the situation, summary of assigned tasks, key actions performed, and the action’s results. Don’t overlook the Result variable of the formula. People often do a good job describing the project and actions taken, but fail to mention the positive results of their actions.

Relevant Experience (5 minutes)
After the project overview, the interviewers will likely ask about your experience as it relates to the project. Assuming you know a little about the project, you can reflect on your experiences and find a related example. If the project management position interfaces directly with clients or business customers, you’ll want to highlight past experiences demonstrating how you connected with customers for effective delivery.

Technical Skills (5 minutes)
The title of “project manager” is often bestowed upon anyone in a leadership position despite their lack of technical project management knowledge. The technical project management question is intended to determine if you really know the science and not just the art of project management. This is an opportunity to highlight your technical experience performing critical chain analysis, calculating earned value, or resource leveling a project schedule.

Soft Skills (5 minutes)
The soft skill question is usually asked to test a project manager’s team management skills and overall leadership behaviors. Look at your experiences and recall examples of conflict resolution, issue management, managing customer’s expectations, and team building. You’ll notice this technique focuses on experiences and not specific positions. Citing experiences from multiple positions is an effective technique to demonstrate breadth.

Wrap Up (5 minutes)
The last five minutes of the interview is your opportunity to ask any questions and inquire on next steps. Remember to reiterate your interest in the position and ask if there is anything else that requires further clarification.
Once you understand the basic interview format, there shouldn’t be too much to worry about. In a 30-minute interview, you’re controlling one-third of the discussion. You know at least one question will be related to the position and the other questions will address your project management background. The format should help remove any nervousness about potential interview questions.
Longer interviews will likely follow a similar format. The PMBOK is also an effective resource to map experiences to potential questions. Scope management, risk management, integration management, financial management and other PMBOK sections are excellent areas for interview questions. Review your experiences and map your professional history against the PMBOK.

The Mind Map
Organizing your thoughts in preparation for the interview can produce a combination of scribbles, scrawls and Post-It sticky notes all over your resume. Using a mind map to document your introduction, elevator speech, key experiences and questions will help you prepare for the interview. Here’s a sample interview mind map:



The basic format of the mind map includes a section for interviewer information, company or project background, your introduction, elevator speech, and recent position summary. Additional topic nodes include a summary of technical management experiences and situational project management experiences. Each example branches into the STAR formula of Situation, Task, Action and Result. The format is simply a guideline. Expand the mind map for the key elements that fit your background and style. The mind map is a quick and easy tool to prepare for an interview. Using the prescribed format and the mind map tool may not remove all pre-interview jitters, but it will help you prepare for a competent discussion. Since the mind map fits on one sheet of paper, you can quickly review your notes a few minutes before the interview and feel relaxed knowing you’re well prepared for a successful discussion.

This article was written by Andy Makar and originally published at http://www.projectsatwork.com

Add a comment
 
<< Start < Prev 1 2 3 4 5 6 7 8 9 10 Next > End >>

Page 7 of 14
Joomla Templates by Joomlashack