Monday, February 23, 2015

Desert Island PM - Stranded With Just One Tool

Good Project Management is all about the basics. A recent super complex project got me thinking about the most essential tools that a PM must rely on every day. If you were stranded on a remote desert island with access to only one PM tool to do your job, what would you choose?

The List

Many people outside of the world of project management think it is all about the classic Microsoft Project GANTT chart. This detailed task breakdown can often take ages to develop correctly using all key SMEs and stakeholders. The management and upkeep of these charts can be a full time job, and many consider them the gold standard for any serious project. While you can't argue with the value of a the GANTT as a project 'book of record', I often rely on a much simpler tool day-to-day to get real results. When push comes to shove, a good PM knows that that good tactical task management depends on your list. All you really need is a smartphone list to create and track lists on a daily, hourly and real time basis. Lists are easily managed by one person, tracking is simple and they do a great job of highlighting the work that really needs to get done right now. A good managed list is the true essence of project management.

The Spreadsheet

Everyone knows the old adage "you can't manage what you can't measure". However, we must not take this too far and end up measuring so many different elements of a project that there is no time, or inclination, to ever make sense of it. Data collected is most useful when it is easily digested by the brains that matter, and that means the brains of your key stakeholders. A simple spreadsheet is an invaluable tool to allow a PM to easily track/update data and then quickly and easily display the results. To this end, it is great to use cloud utilities like Google Spreadsheets which have a feature set that is intentionally minimized/simplified to force you to only use the functions that really matter. The key is to move away from flat spreadsheet files spread around by email and move your team to cloud spreadsheets that provide a quick and easy way to measure, collaborate and get results.

The Deck

No matter what kind of project you are managing, you can't succeed without great communication skills. Knowing what to say, when to say it, and how to say it, is the hallmark of seasoned PM.  A classic Powerpoint-style deck is one of the most vital PM tools to quickly communicate your tasks/progress/results. Not unlike the way a tweet forces you to communicate the essence of your message in 144 characters, a deck has always forced the PM to distill analysis and focus thought. A concise message works great every time whether talking to a senior executive, a new hire or a time-starved technical SME. The key is to follow best practices when creating your decks including clean fonts, liberal use of charts/pictures and simple templates and colours. These golden rules help to keep the message short, punchy and crystal clear.


As a rule, it is great to regularly re-examine your bag of PM tools and tricks to ensure you have the right mix to ensure your success. By considering your own desert island list, you may determine that the simplest tools are the ones that get used every day, and in every way, on your most successful projects.  A great PM knows simplicity is the key to success.
Dave Ullrich, B.Comm, PMP specializes in IT project management consulting and strategy with his company Cilantra Solutions. He has based this approach on the results of several successful IT project implementations with teams distributed across Canada, US, and the UK. He can be reached at daveullrich@gmail.com. 

Friday, October 14, 2011

Instincts – Making the Right Moves

Many people believe that good project management instincts can’t be taught. However, there are simple ways that any PM can improve their game. One definition of ‘instinct’ is a “complex pattern of behavior present in every specimen of a particular species, that is innate, and that cannot be overridden”. In simple management terms, it can be thought of as a person’s natural reflex. Just like an animal in the jungle, a really good PM relies on their instincts to navigate through the unknown.

A PM with good instincts, and good natural reflex, knows when to make a move and when to hold steady. They know when to communicate, and when to protect information. Their instincts tell them who to talk to, and whose talk can’t be trusted. For a good PM, reviewing an org chart is like a doctor reading an x-ray, as it often quickly reveals the true inner workings of any project.

If you’ve ever tried to hire a PM then you know how tough it is to find individuals with that magic combination of clear communication skills, strong project management fundamentals and decisive instincts. The question for young PMs, and organizations looking to make their PMs better, is ‘how can one develop better PM instincts’?

The Bad News

Generally speaking, truly good instincts seem to be a product of one's cumulative life experiences. So, in many ways, you either have it or you don’t. Everything from your earliest social skills learned as child, combined with your work/travel/fun experiences, tend to play into the amorphous concept known as ‘instinct’.

The Good News

On the other hand, it is possible to hone your instincts through experience, mentors and reflection. Being mindful about developing better instincts is the first step to improve. A conscious decision to seek improve your instincts will pay benefits greater than any PM course, university degree or expensive new suit. Developing good instincts will simplify your life, lower your stress and make your projects run better.

Experience

There is nothing like real project experience to help a person understand how the world really works. In each new project, we tend to come across many of the same characters/challenges and experience helps us to react with a more immediate knowledge of likely outcomes. Many times, it really is true that ‘what doesn’t kill you, make you stronger’. PMs that are able to learn from their mistakes will increase their success when faced with similar future challenges. Experience teaches us that there are only so many different ways to approach the same problem, and that no single solution is the correct solution. Instincts improve with experience as we learn to think before we leap, and consider possible ripple-effects of what we do before we do it. Experience is truly innate and it can’t be substituted by any other skill. This is why experienced project managers tend be more trusted, and often have greater project success.

Mentors

A good mentor can help one make sense of confusing, or conflicting, information. The ability of a mentor to sit outside of a situation, and draw on their own personal well of instinct and intuition, can really help younger PMs hone their own instincts. Learning from those that have been in tight spots is a great way to collect valuable intellectual capital that can only come from a one-to-one connection with a senior PM mentor. A good mentor can review various possible ways of handling a situation, apply their own instincts and make go-forward suggestions. This allows the young PM to learn ‘risk free’ by discussing various scenarios, reviewing pros and cons, and then choosing an informed path.

Reflection

Daily reflection is a simple way to improve instincts. A good PM will use a few spare minutes every day, perhaps on way home from work, to engage in some realistic self-review to assess notable daily interactions, decisions and challenges. This assessment will focus on what went right, what went wrong and what could be improved in similar situations next time. This type of self-feedback loop is an ideal way to exercise one’s instincts, like flexing a muscle, every single day of the week. The key benefit to reflection is comprehension. Learning never stops and daily self-reviews are a great way to truly digest the instinctual challenges we have daily.

A PM with good instincts will have more successful projects, receive great respected from their peers and be in high demand. Project managers that leverage the benefits of project experience, mentors and daily reflection will hone their instincts and further grow to become true leaders.

Dave Ullrich, B.Comm, PMP specializes in IT project management consulting and strategy with his company Cilantra Solutions. He has based this approach on the results of several successful IT project implementations with teams distributed across Canada, US, and the UK. He can be reached at daveullrich@gmail.com.

Tuesday, July 27, 2010

Connecting the Dots - Using Program Frameworks to Successfully Link Enterprise Projects

As project complexity increases in the enterprise environment, simple structures are needed to deploy mission critical applications. Program frameworks allow projects to be bundled together using straightforward governance structure, common communication methodology and shared ownership.

A Great Name

A good program starts with a great name. When a single program encompasses several businesses or technology projects, it can be a challenge to get a single name that works to distill everything. However, it pays to take the time to do some crowdsourcing, run a naming contest or engage a design firm to assist. The program name should tie back to the highest overall goals of the program and a quality name brings clarity to the mission of the overall engagement. Most importantly, a great name gets people excited, starts people talking and keeps the program at top of mind across the enterprise among both senior executives and the rank and file.

Simple Governance Structure

Enterprise programs benefit from simple governance structures that can be summarized on a single sheet of paper. The key is to create a series of steering committees and team status meetings that allow information to flow up and down the organization quickly and clearly. If everything can’t fit on a single one-pager, you probably have too many committees, too many teams or too many layers.

Common Communication Methodology

Once again, a one-pager dashboard is vital. Program transparency is greatly improved when you create a document, or website, that provides a single one-page overview of all projects and all common metrics. A regular spreadsheet with simple colour codes, project statistics and key roles/names should be updated every week and presented with all relevant financial reporting. Documentation should be posted using a common platform like Sharepoint, or Google Docs. A communication matrix should be developed to ensure that everyone gets the information they need, when they need it.

Shared Ownership

Shared ownership of a program starts with a common understanding of the overall goals. When clear project goals are defined up front with input from all levels of the organization, all teams can agree on a definition of success. A series of iterative working sessions to develop the program goals creates a conduit for senior management to float competing priorities, gauge reaction from peers/stakeholders, then revise. This ‘survival of the fittest’ process will ensure the ideas really have legs and they will form a solid base for the success of the program.

Simple frameworks are the glue that holds an enterprise program together, working to increase the chance that all program sub-projects are executed with success.


Dave Ullrich, B.Comm, PMP specializes in IT project management consulting and strategy with his company Cilantra Solutions. He has based this approach on the results of several successful IT project implementations with teams distributed across Canada, US, and the UK. He can be reached at daveullrich@gmail.com.

Wednesday, April 29, 2009

Transparency – The Magic of Agile

Projects need transparency to ensure clear project communication. Everyone wants to know just what they need to know, when they need to know it. One of the best things about the Agile methodology is the focus on frequent iterative checkpoints between the development team, management, the sponsor and the customer. This form of connection goes a long way to create greater project transparency and helps a team to more organically readjust requirements to react to changing needs, market conditions and financial restrictions.

Communication Over Documentation

The many variants of the Agile methodology have a common desire to value communication over documentation. The scenario of a waterfall project that spends years in the development of project requirements documentation, only to be cancelled prior to development, illustrates the core communication weakness of waterfall. People don’t know what they don’t know. Short iterative touch points allow all stakeholders to see requirements in action, and make adjustments quickly. The communication loop is simple, direct and sometimes painful.

Communicate Up and Down

From a management perspective, it is still important to communicate in both directions on an Agile projects. As everything moves very quickly, there is a temptation to get caught in the weeds of daily issue management and overall project direction. This is particularly true in the early stages of an Agile project when processes, requirements and development may all be happening at the same time. The temptation is to focus on communicating and connecting with the team. However, this is the stage where the Steering Committee must be kept up to speed on their value for money. Once the early iterations starting flowing through the review and approval stages, the wider team will become more aligned on the larger project goals. Overall project transparency will start to emerge as the development team learns early about the needs and quirks of senior management. Similarly, the steering committee will get a real sense of what kind of work can be achieved in realistic timeframes.

Consistent Approach to Iterations

A simple iteration schedule applied consistently is the best way to ensure transparency. A simple two week loop with checkpoints for requirements planning, design, review, development, QA and deployment acts like a mini circular project plan. Everyone knows exactly what to expect every two weeks and the team will establish a rhythm. As unplanned requirements come up in successive iterations, they get reviewed alongside other project priorities in real time. The loop is tight, clear and effective.

Be Flexible

As the name implies, Agile really is all about flexibility. Project transparency means that everyone knows more about what everyone else is doing. If people know you are doing, you need to be prepared to adjust based on their feedback. Change is constant, and change is good. Getting in the groove of a constant feedback loop will allow you to elevate your project management game with creativity and decisiveness.

Embrace Agile as your window to clear project communication.

Dave Ullrich, B.Comm, PMP specializes in IT project management consulting and strategy with his company Cilantra Solutions. He can be reached at daveullrich@gmail.com.

Tuesday, April 28, 2009

The Thin End of the Wedge - How To Sell Project Management To Disbelievers

Where do you start? Selling project management to disbelievers is a serious challenge when trying to grow an organic project-based culture. Making the case for project management involves knowing how, and who, to influence with the details that matter. How can you get someone to really understand something that they’ve never really seen before? You need the real thing. The greatest advocates of project management are those that have had it work on a project from beginning to end. These are people that have seen several ‘near misses’ averted, but also have a full understanding of the potential impact on the bottom line. Project management works. We all know that, but now we have to prove it to other people. You must tailor the message to your audience, and there are several great ways to make your pitch.

Thin End of the Wedge #1 – Lead by Example

The only way to understand project management is to see it in action. Setting a great example is the best way to demonstrate the benefits that result from a strong application of PM best practices. When projects are new to an organization it is very important to ensure that potential champions witness classic PM form. It is vital to ensure your initial projects have a very well defined beginning and end. In a non-projectized environment, it is very common for work engagements to have uncoordinated starts, and never-ending finishes. Work just happens. In the project-based culture, the key is to ensure both the team, and the larger organization, know exactly when a project has started and finished.

Communicating project timelines, status, and team composition is the best way to stand out from the crowd. For example, you should kick-off your first projects with a splash using several standard team-building tools. The group should work together to come up with a team name, common meeting area, and simple ground rules. Keep the tone electric, and really sell the sizzle. In addition, the initial meeting should be used to strongly define the project roles and responsibilities, scope, and timelines. When the project is complete, make sure you have a final celebration, team gift, and a lessons learned/postmortem. Publicize the project team results by putting a photo of the group in your company newsletter. Although they may not always be fun, projects are new to your organization. Make the novelty work for you by capitalizing on the little successes and work on ‘building the story’ around the growth of the project culture. By providing good form, you provide a concrete reference point for the entire organization.


Thin End of the Wedge #2 – Scope Matters

What is the one thing that you need to know if you have never heard of project management? Scope matters. All projects have a beginning and end, and a good PM must know exactly what has to be accomplished in the given timeframe. Scope must be well defined and clearly communicated to all project stakeholders. Once the boundaries have been clearly laid out, an array of tools and techniques must be deployed throughout the project to ensure the boundaries are protected.

It is important to explain that everyone benefits when the project team sticks to the scope. At any given time in a project, a sponsor may try to add a feature that would benefit her department, product, or corporate profile. Meanwhile, a team member may try to change an element that would make his job easier, be fun to do, or further pad his resume. The temptation to change scope is constant, and the context is usually very personally, and politically, charged. In organizations that are defined largely by functional activities, these types of changes are commonplace. Why? When your job is to do operational work, scope doesn’t really matter. In the project world, the PM must be adept at using issue management, change control, and quality communication techniques to keep the team focused on the project boundaries.

The PM is there to understand the big picture, and promote the long-term project view. Individuals that are focused on short-term objectives, usually suggest small functional changes, causing more ‘scope creep’. The job of the PM is to enable the team to fully understand the impact of out-of-scope changes, and promote the benefits of staying within the project boundaries. Ultimately, nobody on the team wants a project to be over time, over budget, or lacking features. The impact on company, career, and job satisfaction can be very real. The PM helps the team to stay on point, ensuring that maintaining project scope will benefit everyone.

Thin End of the Edge #3 – Accountability

‘Doing what we said we would do’. This pretty much sums up the objective of any well-run project, but project management disbelievers may not agree. It is tough to have accountability without scope, and both are often somewhat fuzzy in operational organizations. We all know individuals that have built a career around transferring, obscuring and denying accountability. The key advantage of project-based work is the ability to better define scope, and therefore better assign accountability.

By clearly defining the roles and responsibilities at the start of the project, it is possible to lay solid groundwork that will encourage more responsibility. Always remember that the ‘project role’ can often be different from the ‘organizational role’, and the distinction must be made very clearly. A team that knows exactly what is expected has a greater chance of success at meeting objectives. The project manager should take the time to personally review the assigned project role with each team member at the start of the project. Feedback should be gathered, allowing the PM to ‘sign off’ on the agreement with each person.

Although someone other than the PM may often assign project roles, it is important that the manager confirm the role with the individual. Remember that the best work assignment is always an agreement between the manager and the team member. Individuals that have a stake in the decision about role definition always appreciate the ability to better define their work. This is great for the team, and further strengthens the PM’s ability to ensure accountability.

Patience and Subtlety

Slow and steady. Organizational change is always best achieved through gentle execution of a well-planned set of objectives. Selling project management in an entrenched functional organization will always be tough. The key is to stick to a few simple principles, and work to the goals with patience and subtlety. To lead by example, patience is needed to allow several initiatives to pass through the full project lifecycle. Once the results are real, it will be easy to champion the success. The process of promoting scope and accountability in a functional organization will require a subtle approach to minimize the potential for ‘organizational shock’. The move to a project-based culture will really shake things up, and the wise PM will recognize the importance of treading lightly. Selling project management to disbelievers is a challenge that can be met when we stick to the vision, and work smart.

Article originally published in May 2008.

Dave Ullrich, B.Comm, PMP specializes in IT project management consulting and strategy with his company Cilantra Solutions. He can be reached at daveullrich@gmail.com.

Technology and Team Building - Making Remote Project Management Work

Everyone knows that the best project managers are ‘hands on’. The discipline of project management requires the ability to facilitate complex interaction between schedules, budgets, technologies, and people. When these elements are geographically dispersed, the inevitable challenges to project success become much greater. To make it work, the remote team project manager needs to implement specific techniques that address the inherent weaknesses and strengths of these initiatives. An effective and creative approach to managing remote teams will increase the chance of doing the impossible.

How do we end up with remote project teams?

The global marketplace, sophisticated communication technologies, the demands of a skilled workforce, and the ever-increasing drive for cost efficiences mean that remote teams are a new fact of life. These teams may result from the use of stay at home workers, offshore development resources, or just the simple need to link skilled people and create valuable project results. How do you make it work? Communication is the essence of good remote team project management.

The Internet is the key

The Internet facilitates quality team communication. We must remember that the Internet was originally created by the US military to facilitate research and development activities among geographically dispersed project teams. Today, we’ve refined our use of the Internet as a communication tool so that it can fully support the needs of the modern project team. Collaboration is key. Tools such as email, VPN, instant messaging, whiteboards, text messaging, online conferencing, and project websites combine in allowing project managers to assist the progress of real collaborative results.

The electronic breadcrumb trail

Internet collaboration technologies promote accountability. Remote teams live and die by the ability to balance individual creative output with constant access to the quality intellectual production of the rest of the team. Remote work usually means that team members are able to remain in work environments that are creative, sensible, or at least convenient. Some of the best technology workers make the conscious decision to exist in environments far removed from major cities. This can be a win-win situation if the right environment is set up to allow the team to thrive, along with assurances to project stakeholders that the work is getting done. Internet collaboration tools create an effective and useful breadcrumb trail that brings real transparency to the project process.


How does the technology work?

Internet communication tools facilitate quick, meaningful, and efficient distribution of project information. In addition, the results effectively create an archive of project decisions, developments, and knowledge. Project information can easily be collected, managed, and reviewed by all members of the team.

A simple tool such as a team email list quickly allows individuals to disseminate information to the full group with one quick message. These lists create instant discussion threads that are easy to read, and tough to miss. Instant messaging tools provide an efficient means of getting answers for quick decisions that don’t require a full email or phone call. In addition, instant message software uses status icons that say ‘I’m here’. With a simple team rule that makes it a daily requirement to post this icon, you can feel more confident that your team is on duty. Virtual Private Network (VPN) software allows individuals to access remote computer systems using simple encryption technologies. This software facilitates safe access to high security internal networks when team members are just about anywhere, yet they are still ‘in the office’. Web conferencing and ‘whiteboard’ technologies allow project managers to hold remote meetings via the Internet with full access to real time display technologies. These tools allow a PM to use techniques that facilitate real interaction and team development. Text-messaging and “always-on” email tools, like the BlackBerry pager, permit real time communication almost anywhere. Finally, a high quality project web page is a great way to wrap it all up. The project page can act as the key interactive resource for capturing all information related to the project. This includes information updates, status reports, documentation archives, and access to all information threads. Although Internet technologies create a solid collection of project development activities, a bit more will be needed to make it really work.

Conventional Collaboration Tools

There is no substitute for a real face-to-face meeting. Due to the obvious complexity and cost associated with gathering a remote team, it is important to be judicious about the timing and technique. Meeting in person with the project team is most effective at the beginning, and end, of a project. In addition, get-togethers focused on the completion of major milestones underline project progress for both the team and sponsor. The good news is that these meetings are often an effective method of creating a ‘clearing house’ for the collection of major issues that have been skillfully and thoroughly tracked using the Internet technologies. The results are real. Daily team conference calls are also a great conventional method of facilitating communication and issue resolution with the team. The meetings can be short, no longer than 30 minutes, and the PM should facilitate discussion around the highest priority issues. The calls provide a chance for the team to ask the types of questions that just don’t translate in electronic form. Junior team members respond well to the quality of daily discussion among the team leads, and the result is a valuable mentorship tool. These conventional collaboration tools help to build superior teams.

Team-building on a remote project

Teams love information. Developing the team dynamic for a remote project team is facilitated through the effective and coordinated distribution of information. There are many creative ways to use these collaboration tools to build team development. Daily conference calls should be used as an opportunity to foster small talk, and provide friendly windows into the world of the team. A daily ‘word of the day’ or ‘in the news’ segment is a great way to set the expectation that non-project interaction is encouraged. An in-person project kick-off meeting provides an opportunity to put a face to a name, and allow the team leads to assess the true skills of the project team. The impressions made at this meeting will mold the development and growth of the team dynamic.

Although you may not be able to celebrate every milestone in person with your team, it is possible to find simple ways to remotely reward your group. Home delivery can be your remote sets of arms, used to hand deliver gifts and words of encouragement. Something as simple as a surprise pizza delivery, junk food basket from an online grocer, or local movie tickets will go over big with the team. Although you can’t be there, the team will readily get the message that results count.

Results that really matter

Remote teams can make everyone look good. This approach to managing teams will only become more common as communication tools continue to improve. As the frameworks get better, the cost and quality benefits of remote teams will become harder to ignore. Whether the context is offshore development, the use of home offices, or increasing global collaboration, remote projects must be executed successfully. Project managers have a great variety of collaboration tools available to make it work. It is possible to keep a ‘hands on’ approach with remote team project management.

- Article was written for Gantthead in 2003.


Dave Ullrich, B.Comm, PMP specializes in IT project management consulting and strategy with his company Cilantra Solutions. He has based this approach on the results of several successful IT project implementations with teams distributed across Canada, US, and the UK. He can be reached at daveullrich@gmail.com.

Monday, April 27, 2009

Making Meetings Matter - How To Run Effective Meetings

To make meetings really matter, you just have to be simple and consistent. After all, managing effective meetings is the quickest way to gain credibility with your team and drive real project results. It is vital to prepare well for every meeting, and sincerely value the time contribution of each and every member of your group.

Here is a checklist that will focus your planning:

- Always start on time.
- Always have an agenda.
- Always clearly communicate the purpose of the meeting.
- Always clearly communicate the desired result of the meeting.
- Always set a specific duration for the overall meeting, eg. 1 hour
- Always time each of the major topic areas, eg. Introduction – 10 mins.
- Always pick a Meeting Chairperson.
- Always set the clear expectation that the Chairperson will be the ‘traffic cop’, working to keep the meeting on topic, and on schedule.
- Always provide the opportunity for the group to add to the agenda at the beginning of the meeting.
- Always manage your group to stick to the time estimates.
- In the event that the schedule is slipping throughout the meeting, ensure that you use the final ten minutes to drive for close on key topics. Call for a pause in the action, review what absolutely needs to be addressed in ten minutes, and then work to complete.
- Always reschedule a follow-up meeting if all topics can’t be covered within the scheduled timeframe.
- Always track a list of Action Items throughout the meeting. This includes issue, person responsible, and due date.
- Always summarize Action Items for the group at the end of a meeting.
- Always take Meeting Minutes. All that is required is a collection of simple notes on key points.
- Always follow-up with Minutes in email, or just the list of Action Items.
- Always keep your meetings as short as possible.
- Always finish on time.

Strong meeting management is a skill appreciated by anyone, anywhere, anytime.


Terry Scott is a Technology Project Management specialist who is passionate about process. He can be reached at terry@scottfree.ca.