Category Archives: Journey to the Cloud

Active Project Management; Facilitate, Don’t Dictate

It is estimated by the Project Management Institute that 90% of project management is communication. The tasks involved with setting up a project, identifying sponsors, defining resources, schedules, managing risks, and critical paths are all important elements of large complex projects. Facilitating the team’s communication channels is the single most important effort of a good project manager.

Rudyard Kipling once wrote “… the strength of the Pack is the Wolf, and the strength of the Wolf is the Pack.”

A wolf has to support the pack but also has to be able to survive on its own abilities. When building project teams the goal is to assemble a “pack” with different strengths and opinions that can perform at their own peak level. A high performance pack has strength through the members of the project team.  An effective Project Manager needs to assemble individuals into a pack (or work with an existing pack), provide constant and useful communication, and assist as needed to guide them to their end goal together.

Five tips for building a better wolf pack:

  1. Listen
  2. Value ideas
  3. Positive thinking
  4. Try to close all conversations by asking what you can do to help
  5. Have a sense of humor

Preparing for project kickoff meetings creates an opportunity to listen to the team and get them engaged. An important part of pre-planning a successful kickoff is soliciting the team’s input and providing opportunities to talk about the project’s risks, schedules, and goals. The sooner the project manager begins to listen to the team rather than detailing his or her own thoughts on the project, the more likely and quickly the team will become engaged. Soliciting input from a diverse set of stakeholders substantially increases the chances of full engagement of the project team.

In addition to the project management role of ensuring the project meets the triple constraints of Scope, Time and Budget, taking an approach as a facilitator and understanding and deploying your team as a collaborative resource and working to integrate their skills will provide a more complete 360 degree, holistic view to the project. The project manager plays an important role in encouraging and engaging opportunities for collaborative conversations. The team’s input will allow for better commitment and buy-in from the stakeholders and the team, and ultimately better position the team to successfully meet pre-defined project objectives.

A Project Manager needs to rely on previous project experiences as well as foundations built from credentials (e.g. PMP certification). Often, tasks don’t flow exactly as expected and decisions are often made outside of planned meetings; however it is important to leverage meetings as a means to collaboratively check-in with the team on any decisions made, the impact of the decisions, and to establish meeting minutes as the reference point for the projects. The meeting minutes provide an important, literal “power of the pen” which enables Project Managers to lead and guide the project team.

On a recent Virtual Desktop Infrastructure project installation, there was a new member representing the customer’s infrastructure function, and this caused a sudden shift in the project deliverables. While a customer is not always right, the customer is most certainly paying for your ability to understand, adapt, and communicate changes within the team and manage to the approved Scope. In this particular example, the focus shift was remediated by adjusting weekly meetings to a daily standing meeting which provided for relevant and timely inputs and buy-in from the diverse team members and allowed for a very quick process adjustment and consensus for achieving Scope deliverables.

A Project Manager also relies on the team to identify critical project information in order to ideally circumvent any issue before problems may occur. When issues do occur, facilitating conversations and soliciting input from the team, both informally and formally, are usually far more effective than a project manager declaring a solution. A project team where teamwork, loyalty, and communication are the norm can provide a “howling” successful project.

 

Going Rogue: Do the Advantages Outweigh the Risks?

Are all rogue IT projects bad things? Could this type of activity be beneficial? If rogue IT projects could be beneficial, should they be supported or even encouraged?

Recently, I took part in a live Twitter chat hosted by the Cloud Commons blog (thanks again for the invite!) that was focused on Rogue IT. After hearing from, and engaging with, some major thought leaders in the space, I decided to write a blog summarizing my thoughts on the topic.

What does “Rogue IT” mean anyway?

I think that there are rogue IT users and there are rogue IT projects. There’s the individual user scheduling meetings with an “unauthorized” iPad. There’s also a sales department, without the knowledge of corporate IT, developing an iPhone app to process orders for your yet-to-be-developed product. Let us focus on the latter – rogue IT projects. Without a doubt, rogue IT projects have been, and will continue to be, an issue for corporate IT departments. A quick web search will return articles on “rogue IT” dating back around 10 years. However, as technology decreases in cost and increases in functionality, the issue of rouge IT projects seems to be moving up on the list of concerns.

What does rogue IT have to do with cloud computing?

Cloud Computing opens up a market for IT Services. With Cloud Computing, organizations have the ability to source IT services to the provider that can deliver the service most efficiently. Sounds a lot like specialization and division of labor, doesn’t it? (We’ll stay away from The Wealth of Nations, for now.) Suffice to say that Rogue IT may be an indication that corporate IT departments need to compete with outside providers of IT services. Stated plainly, the rise of Cloud Computing is encouraging firms to enter the market for IT services. Customers, even inside a large organization, have choices (other than corporate IT) on how to acquire the IT services that they need. Maybe corporate IT is not able to deliver a new IT service in time for that new sales campaign. Or, corporate IT simply refuses to develop a new system requested by a customer. That customer, in control of their own budget, may turn to an alternative service offering “from the cloud.”

What are the advantages of rogue IT? Do they outweigh the risks?

Rogue IT is a trend that will continue as the very nature of work changes (e.g. long history of trends to a service-based economy means more and more knowledge workers). Rogue IT can lead to some benefits… BYOD or “bring your own device” for example. BYOD can drive down end-user support costs and improve efficiency. BYOD will someday also mean “bring your own DESK” and allow you to choose to work when and where it is most convienent for you to do so (as long as you’re impacting the bottom line, of course). Another major benefit is increased pace of innovation. As usual, major benefits are difficult to measure. Take the example of the Lockheed Martin “Skunkworks” that produced some breakthroughs in stealth military technology –would the organization have produced such things if they had been encumbered by corporate policies and standards?

Should CIOs embrace rogue IT or should it be resisted?

CIOs should embrace this as the new reality of IT becoming a partner with the business, not simply aligning to it. Further, CIOs can gain some visibility into what is going on with regard to “rogue IT” devices and systems. With some visibility, the corporate IT departments can develop meaningful offerings and meet the demands of their customers.

Corporate IT departments should also bring some education as to what is acceptable and what is not acceptable: iPad at work- ok, but protect it with a password. Using Google Docs to store your company’s financial records…there might be a better place for that.

Two approaches for corporate IT:

– “Embrace and extend:” Allow rogue IT, learn from the experiences of users, adopt the best systems/devices/technologies, and put them under development

  • IT department gets to work with their customers and develop new technologies

– “Judge and Jury:” Have IT develop and enforce technology standards

  • IT is more/less an administrative group, always the bad guy, uses justification by keeping the company and its information safe (rightly so)

CIOs should also consider when rogue IT is being used. Outside services, quick development, and sidestepping of corporate IT policies may be beneficial for projects in conceptual or development phases. You can find the transcript from the Cloud Commons twitter chat here: http://bit.ly/JNovHT