Improving Productivity – Suggestions from PMI

If you have not wandered through the Project Management Institute’s (PMI) knowledge center, you have missed an excellent source of best-practice thinking on a variety of issues relevant to project and corporate management. Recently I reviewed an article by Pradeep Patra, PMP and Sunitha Bartaki, PMP of Tata Consultancy Services Limited that I thought was interesting. The article titled, “Productivity Improvement Using Ten Process Commandments” can be found in its entirety here.

At the beginning of their article, they note that productivity improvement is never ending, as discussed in writings on Kaizen and the philosophy of continuous improvement. Productivity improvement initiatives can also be costly. Therefore, their first recommendation is to develop and use a cost of quality (CoQ) to evaluate the impact of changes designed to improve productivity.

Their productivity commandments are:

  1. Leadership commitment
  2. Manage change — Absolutely, I agree. Productivity improvement requires change and to succeed at managing change requires the active support of visionary leaders. (see previous posts on change management: Change Management Strategies, Role of Project Managers in Change Management, and Planning Your Organizational Change.
  3. Organize and plan — can I say, “duh.” However, they continue the “organize and plan” discussion by recommending that the organization create a prioritization of changes — just like ranking software change requests — and that individuals create and monitor early warning signs of problems as part of risk management. OK, that is a very good thing for all organizations to do.
  4. Reward people for contributing to the productivity improvement process.  You have to incentivize people if you want them to change and try new things.
  5. Train the leadership team, participants, customers and clients. The better stakeholders understand the productivity improvement process, the more valuable will be their support and contribution.
  6. Create a process improvement framework for project managers, engineers, process managers and support personnel. If the cultural change required is significant or the suggested improvement costly, complete pilot studies or small implementations before spreading across the entire organization.
  7. Measure key variables -  this goes without saying for any initiative you try to implement.
  8. Assess and evaluate — “evaluate what you want because what gets measured gets produced.”
  9. Improve communication – I have written several posts on the importance of communication.
  10. Focus on benefits — measure cost savings following these do’s and don’t’s:
    1. Do: assign representatives from finance to validate the initiative and remember to include soft benefits that indirectly affect profit, like customer and employee satisfaction.
    2. Don’t: make productivity improvement another name for cutting costs, nor set unrealistic targets that doom the initiative to failure.

Although the recommendations seem simplistic — and you have heard it all before — the suggestions for a successful productivity improvement initiative are valid.

Finding a Content Management System Solution – Part 2

Last week in part 1, I talked about selecting a content management system (CMS) (which has many names like records management or knowledge management) from a technical perspective. However, just as with any productivity-enhancing tool, the process does not end with getting the tool. Rather, the process begins by understanding the value of content management to the organization and ends with training, acceptance and implementation. If your organization truly wants to benefit from content management, there must be changes in “business-as-usual”.

Your organization will need to have all of the stakeholders participate in any project to implement a CMS so you should be prepared to involve business units, legal, finance, contracts, marketing, operations, human resources, PMO and any other groups who have a stake in the information flow of your organization.  You will also need a plan for the implementation project so that you can achieve outcomes that are beneficial to the organization.  To quote Lewis Carroll, “If you do not know where you are going, any road will get you there.”

In 2006, Dr. Karen McGraw, CEO of Cognitive Technologies, suggested 10 questions decision makers should answer before committing resources to content management system solutions (Dr. McGraw’s complete white paper):

  1. What content do we need to manage better or use more effectively?
  2. What types of content management initiatives are we involved with already?
  3. Where is the greatest impact for content management efforts?
  4. Where are the best opportunities to achieve business value and ROI?
  5. Where are we in terms of content management maturity?
  6. What kind of technical infrastructure is required to support content management?
  7. Are we prepared to implement and manage the cultural changes that may be required for content management to be successful?
  8. What are the characteristics and competencies our employees will need to succeed with content management?
  9. Does our content management initiative support our strategic business objectives?
  10. Am I providing the required leadership and support to ensure the success of content management initiatives in my organization?

Dr. McGraw emphasizes the point that implementing a content management system should not be undertaken lightly or perfunctorily if benefits are to be achieved. In my experience, the key to success is user acceptance. If staff members see value — or potential value — in content management, they will expend the time and effort required. If users do not anticipate gaining any direct benefit, they may perform only the minimal tasks needed to comply with the process. Worse, they may sabotage the system through inattention to detail, refusing to use the system or discouraging others.

Getting User Buy-in
The value of implementing a content management system may not be intuitively obvious to all employees when considered in light of their current job tasks. In addition, seasoned veterans of other management initiatives may sigh with foreknowledge that they will have to do something more and different. Therefore, it is up to management to sell a vision of the content management systems benefits to the organization and to individual workers.

Here are seven tips that will stimulate employee buy-in:

  1. Get a representative group of users to participate in setting up the CMS — identifying the source documents and agreeing on the tags and taxonomy — classification scheme — that they would find helpful when searching for information
  2. When rolling out the CMS initiative, use stories and examples of time saving and quality improvements that tie directly to the work being done by individuals in the audience
  3. Offer incentives for early adoption
  4. Ensure that managers and leaders serve as role models in using the CMS
  5. Provide training
  6. Make sure the tools provided by the CMS offer easy-to-use mechanisms for the employees to add and describe content
  7. Plan and implement a process to keep content updated and well organized (read that as tools, responsibilities and information). Nothing turns off users like outdated materials or hard to get to information.

Managing Change
Implementing a content management system across the board yields many benefits to the organization in capturing and accessing knowledge. However, a CMS based system requires changes in business-as-usual. Your organization can learn from other successful change management strategies to successfully transition to effectively using your new CMS.

In the past I have talked about change management and you will find some helpful hints and practices here: Role of Project Managers in Change Management, Project Management PMBOK – Monitoring and Change Control, and Planning Your Organizational Change. Best practice suggestions for change management include:

  • Have a plan
  • Involve key stakeholders and keep them informed
  • Use small projects or departments to test the CMS and polish any rough points before rolling it out over the entire organization
  • Expect resistance — because some people just fight change of any kind. Understand the source of their concerns and address them:
    • The known is comfortable
    • Change requires thought; many current work behaviors have become automatic and require no conscious effort
    • Some people resist change in principle
    • Change is scary—you don’t know what you will win or lose
    • You may fail in the new world order
  • Develop outcome measures to evaluate the CMS
  • Seek assistance from change management experts either in your own HR department or ask for outside training or coaching
  • Offer training
  • Reward effort

If you and your organization have implemented a CMS, please share your experiences and suggestions to facilitate success.

Next, in part 3 of this discussion, I will address one of the most important aspects of a content management system – what do you do after the implementation to maintain the effectiveness and use of the CMS?

Professional ScrumMaster Class Offered in Austin Texas

I have written and spoken in the past about agile and the incremental approaches to building solutions.  I am learning more about SCRUM and how it can improve our ability to be successful in our projects.  Scrum provides a framework for software development that is incremental and iterative. Scrum is based on agile principles that involve planning and implementing software deliverables in short time cycles. As described by Ken Schwaber and Jeff Sutherland in “The Definitive Guide to Scrum: The Rules of the Game,” Scrum is simple to understand and “extremely difficult to master.”

As with other agile methods, Scrum works well in development efforts where requirements change frequently and objectives can be broken down into tasks that a team can accomplish in days rather than months (and most of us have experienced the constant requirements change problem). The role of a project manager in an agile development differs from the role served by managers operating under traditional waterfall methods, as discussed in Agile and project management – Advice from the warriors and now a formal certification in the PMI Agile Certified Practitioner (PMI-ACP).

A project using Scrum framework and methods is comprised of a product owner, the execution team and a “ScrumMaster”, who solves problems and facilitates execution. The Wikipedia write up on Scrum states, “The ScrumMaster ensures that the Scrum process is used as intended. The ScrumMaster is the enforcer of rules. A key part of the ScrumMaster’s role is to protect the team and keep them focused on the tasks at hand.”

I am excited to announce that my organization, Cognitive Technologies, in partnership with Improving Enterprises, is offering the Professional Scrum Master (PSM) certification course in Austin Texas. I am planning on going, so that I can increase my knowledge and skills.

The next class is being held in Austin, TX on December 6-7, 2011. Taught by Don McGreal, the 2-day class is the first significant update of the Certified ScrumMaster (CSM) course that Ken Schwaber introduced and shared in 2002. As in the original, the framework, mechanics, and roles of Scrum are covered. The course then goes further by teaching students how to use Scrum to optimize value, productivity, and total cost of ownership of systems and products. Students will learn through instruction and team-based exercises, and will be challenged to think on their feet to better understand what to do when they return to their workplaces. If you or your organization is trying to use SCRUM then you need to send someone to a course like this.
Here are some details from the course information:

Structure of the Course

  • Scrum Basics – What is Scrum and how has it evolved?
  • Scrum Theory – Why does Scrum work and what are its core principles? How are the Scrum principles different from those of more traditional software development approaches, and what is the impact?
  • Scrum Framework and Meetings – How Scrum theory is implemented using time- boxes, roles, rules, and artifacts. How can these be used most effectively and how can they fall apart?
  • Scrum and Change – Scrum is different: what does this mean to my project and my organization? How do I best adopt Scrum given the change that is expected?
  • Scrum and Total Cost of Ownership – A system isn’t just developed, it is also sustained, maintained and enhanced. How is the Total Cost of Ownership (TCO) of our systems or products measured and optimized?
  • Scrum Teams – Scrum Teams are self-organizing and cross-functional; this is different from traditional development groups. How do we start with Scrum teams and how do we ensure their success?
  • Scrum Planning – Plan a project and estimate its cost and completion date.
  • Predictability, Risk Management, and Reporting – Scrum is empirical. How can predictions be made, risk be controlled, and progress be tracked using Scrum.
  • Scaling Scrum – Scrum works great with one team. It also works better than anything else for projects or product releases that involve hundreds or thousands of globally dispersed team members. How is scaling best accomplished using Scrum?

Audience
This training is primarily targeted at those responsible for the successful use and/or rollout of Scrum in a project or enterprise.

Prerequisites

  1. Have read one of the Scrum books.
  2. Have studied the Scrum Guide at www.scrum.org.
  3. Understand the basics of project management.
  4. Understand requirements and requirements decomposition.
  5. Have been on or closely involved with a project that builds or enhances a product.
  6. Want to know more about how Scrum works, how to use it, and how to implement it in an organization.

Cost

This class is normally $1,495 for the 2 day class, but Cognitive Technologies is offering a discount for early signup.To sign up for the course go to http://www.cognitive-technologies.com/products/training/scrum.aspx.

It is time for us to get serious about learning new methods for projects so I encourage you to look at all of the methodologies that are out there today. If you have more information about this type of training or Agile methods, feel free to leave a comment.

Follow

Get every new post delivered to your Inbox.

Join 383 other followers