Posts Tagged ‘SharePoint’

The Winner Is… itensil

As I discussed in our last post, “A Consultant’s PMO”, we are looking for a PMO (Project/Program/Portfolio Management Office, take your pick) tool to form the core tool to help manage the business of the Centivity group. That is a group of independents that function as a single market entity that I’m affiliated with. Based on our selection criteria we have selected the Knowledge Apps™ tool from Itensil.

What we’ll do in today’s post is examine why we made this decision. Clearly, Itensil is not a household name and they certainly aren’t a large company so why would we make this decision. I believe there are some interesting answers.

The first thing to remember is that we are looking for a tool to manage a collection of projects, resources, documents and manage a collection of proposals, including the creation of those proposals. Consultants have to find work before they can do it. When we include the creation and management of proposals into the mix we extend the scope for our tool beyond just a traditional PMO application. We must also have the ability to manage resources and their activities that are not associated with any projects. Also, we have no expectation that one tool will do everything. Our goal is to minimize the portfolio of required software.

First we must decide how to minimize the required software. To do that we have to decide what functionality is needed in each tool. Besides the list of requirements identified in the last post, we need accounting functionality and project scheduling functionality. We need for the selected tool to connect with an accounting package. For the SMB (Small to Midsize Businesses) we chose Intuit QuickBooks for starters. It is not an elaborate tool but will service our needs. Other tools may be used instead of QuickBooks based on client requirements. As for project scheduling, I confess I’m a Microsoft Project bigot. There are many other tools and several are web-based. However, Project has been around for a long time, has many users and is a solid tool for most projects. It may run out of gas for very large projects and it may be overkill for very small projects. It is still a great overall standard for the majority of projects that we’ll run into. It too can be replaced based on client requirements.

For us, workflow is actually fairly significant. We need to standardize our business processes so we’re not reinventing how we do business with every project and proposal. That is a typical problem with small companies. We must position ourselves for an active future. Being able to incorporate automated workflow into our tools is very important, if not essential.

Now let’s focus on the available solutions. Before we start I want to acknowledge that many of you can provide many alternatives to the field of candidates we chose. We make no claims that our process was exhaustive. It did include representation of the major solution types of interest to us, like minimum cost, maximum project management features, strong document management and collaboration capabilities. First up is Google Docs. It is definitely the low cost leader. We are definitely very budget conscious so this was an early leader. However, it runs out of gas on many fronts very quickly. It’s OK for light document management and can provide some project management capabilities but, frankly, won’t build a lot of confidence in our prospective clients. It may be useful to get started but doesn’t meet the client sniff test.

Now let’s consider a Microsoft Exchange/SharePoint solution. This approach is very capable for document management, proposal management and non-automated workflow management. It’s fairly expensive and we’re pretty much on our own for doing the plumbing connections to other apps (obviously we can always hire help). This approach is not intrinsically cloud-based so there are some IT management requirements. We don’t need to worry about those things for a while. It would produce very capable tools but there would be more up front work than we want.

Next is the Project in a box solution. This is very much a document-centric approach with a heavy focus on lean project management. It is not intrinsically cloud-based which, like the Microsoft-centric approach, means more IT management. While having DSDM Atern artifacts built in is a big deal to me, it doesn’t provide a good all around solution. Connecting other apps to it is problematic. The fact that it is supported out of the UK is very inconvenient, not a deal killer but definitely a problem.

Finally, we’ll consider the Itensil Knowledge Apps™ approach. Their Knowledge Apps tool is basically a framework that is, in turn, customized to the customer’s requirements. That customization is remarkably easy and fast. Their basic offer includes a customized Knowledge App to help us get going quickly. They are cloud-based and, therefore, easily accessible by all of our project resources regardless of location. Workflow is built in, as shown in the diagram on the right, which is a huge deal for us. Wiki-based document management is strong, making collaboration on projects and proposals very easy. It can manage proposal creation as a project and supports other forms of collaboration as well. They can help us with connecting the plumbing to other apps as well.

On the downside, they are a small company and there is some risk there. We have made arrangements with them that will mitigate that risk to our satisfaction. On the upside, they are a small company which makes other small companies (like us) a big fish in their pond. That’s a good thing. It offers functionality similar to Microsoft SharePoint Workspace 2010 in a cloud-based format. That is another good thing.

Overall, we were impressed with the tool. We like what it is now and what it will become. Everyone on our side was excited with what they saw during the demo. Oh yes, and we like the price. It’s one of the more affordable tools which is a big thing to us small companies. I also believe that we have a good relationship with their management. I think they’ll deliver on everything they’ve promised. We’ll keep you posted.

This post has run over my word limit so I’ll stop now. I believe that we’ve made the right decision for our PMO needs. We are looking forward to customizing the Knowledge Apps framework and working with Itensil to grow their product (the big fish in a small pond effect). Let me know if you have any questions.

Stay tuned for more…

Alignment to the Core

Let’s start by being very clear. For any business everything must ultimately align to the success of that business, period. That being said we can now focus on how all of the various pieces that make up that business must align with each other. At a high level, it is obvious that all business activities must support each other for the business to be successful. However, what I have observed over the years is that alignment is easy to get lost in the multitude of daily pressing details that we must deal with. This thought was best captured in Stephen Covey’s book The 7 Habits of Highly Effective People. In this book there is one diagram that has stuck with me over the years because it is direct and simple. It is shown in Figure 1.

Covey matrix 

 

  

  

 

 

  

  

Figure 1 Covey’s time management matrix
 

For more information on Covey’s teachings look here. In this diagram we see Quadrant I as the place where most of us spend much of our time. Quadrant II is where we need to spend most of our time. We need to manage our time such that we can spend more of it thinking about planning, relationships and collaboration. Spending our time here is where alignment happens. We won’t spend any time on Quadrants III and IV. We are wasting our time there.
So what else do we need to consider when aligning our business operations? I argue that we must first understand that all things technology can best be represented as a circle bisected into two parts. One part includes the tools; the hardware and software that enable our business to function. The other part includes how those tools are used to deliver real benefits to our business. Each of those parts is dominated by very different states of mind. Historically, IT has focused on tools and the business users focus on their application. There is overlap for each group as shown in Figure 2.
People

  

  

 

  

 

  

  

 

Figure 2   All things technology and interest groups

The overlap between the interests of those two groups is important. The end user group must understand the tools well enough to know what can actually be accomplished in a reasonable period of time and the IT group must understand the needs of the user group well enough to deliver useful tools. Orchestrating the communication between these two interest groups is an ongoing activity between end customers of the tools and those people who must deliver those tools to the marketplace. It is a painful and inefficient process constrained by the financial interests and negotiating positions of each group. It’s beneficial to each group to make this process more effective.
We must also consider the methodologies that are needed for the alignment of business improvement work. For this we will focus on two of the most representative methodologies for their respective interest groups. For the tool provider group we will use RUP, or Rational Unified Process, as the most used (in its multiple variations) and for the end user community the BPM-based methodologies. The overlap diagram is shown in Figure 3.

Methodogies

 

 

 

 

 

  

  

  

Figure 3   All things technology and improvement methodology overlap
 

The key difference here is that BPM is about addressing what business processes are needed and the functionality of the tools each business needs. On the other hand, RUP is focused on the effectiveness of software development. Delivering business process improvements will consist of new capabilities delivered by some combination of revising the current tools used by the business, buying new software and writing new software. Neither BPM nor RUP alone is suitable for doing that, so managing the overlap between those two families of methodologies is crucial.
 

Finally, there is the overlap between those groups responsible for the day-to-day operation of the tools and those responsible for their daily application. That overlap is shown in Figure 4. Execution 

 

 

 

 

 

 

  

  

Figure 4 All things technology and daily operations
 

The group responsible for the delivery of those technology tools to the business, either internal IT or external, hosted providers is represented by the ITIL, or IT Infrastructure Library, framework. The group responsible for the daily use of those tools is represented by the various continuous improvement frameworks, such as Six Sigma. Each of these groups needs some framework around which to manage daily operation and incremental improvements. Again, managing the overlap of these two interest groups and their frameworks is extremely important.

In each of the cases above, managing the overlap of the various interest groups is a matter of ongoing communication. That communication must happen within an oversight group composed of representatives of each of the interest groups with shared vocabulary and skills inventory. None of the groups need to be experts in the other’s fields but they must commit to understanding the basic needs and issues. This can be a challenge in most organizations but it is vital if the business wants to improve.

Alignment is important and complex. It requires a commitment from a business’s leadership to insure ongoing communications between the core groups within the company. It requires a commitment to include vendors, external service providers and other external stake holders in that collaboration in a meaningful way. So how do you do that? The options are growing every day. There are portal frameworks, like SharePoint and WebSphere. There are peer-to-peer tools, like Groove and Notes. There are Web 2.0 tools, like Huddle and Zoho. The list goes on. Regardless of what tools you use, the ongoing collaboration between the consumers of technology tools and the providers of those tools, both in improvement activities and ongoing daily operations is vital.

Thanks for your attention. Stay tuned…


Structuring your team for BPI sustainability

All business process related projects require some form of team to execute the work. Even for small companies with very informal and centralized leadership, BPI teams exist. They may not be formal but to improve their business processes they need a diverse skills inventory to look at the challenge from multiple points of view. The structure of those teams is extremely important. Insuring the appropriate mix of skills needs to be carefully managed by the company’s leadership to include the perspectives of business operations, information technology, staff functions and external stakeholders. Those external stakeholders may not participate the same way or to the same extent but the needs of customers, vendors and supply chain partners need to be included.

Historically, many business process improvement (BPI) projects fail to sustain their initial gains over the long term. Typically, this happens when the key resources needed to sustain your BPI benefits are overwhelmed by the crush of daily, urgent tasks. Over time, the automated part of the business practices may stay in place but the behavior of the people changes. To address this StrAIT Advisors recommends:

  • Create a collaborative environment

Create a site on your company’s network (portal or something similar) where team members can collaborate, collect new ideas and monitor BPI success. Examples of useful tools are Microsoft SharePoint, Microsoft Groove, IBM (Lotus) Notes/Domino and Oracle Beehive.

  • Project team becomes a business process competency center

Keep your team focused, even after the project is over. Put some level of accountability in their performance plans to spend a portion of their time managing and collaborating on your business processes from a companywide perspective. Remember it is possible to optimize individual departments but sub-optimize the company as a whole.

  • Team leader is on the COO succession plan

This is often overlooked. Your business processes are the lifeblood of your company. The Chief Operating Officer (COO) or equivalent has the primary responsibility for making sure all the wheels keep turning smoothly. The person responsible for your company’s business process “think tank” will gain a wider perspective on how your business works, reinforcing the experiences that put them on that succession plan in the first place.

Categories
Archives