paulg

Lessons Learned about Project Management Offices

0
Filed under Corporate Culture, Developing Teams

If you’ve ever been in a management or leadership role on a project  (and yes, there is a distinction between management and leadership), I’m sure this list will resonate with you. This is a compilation of published Lessons Learned by Derry Simmel, a North Carolina project manager.

These are the 10 most common Lessons Learned by enterprise project teams, as reported and published by their PM Offices.

1. The people we had were great; there just weren’t enough of them.
2. We left management and planning unattended for too long.
3. Unclear roles and responsibilities led to confusion and loss of precious time.
4. We had the most success when we were all informed.

Read More »

paulg

The Programming Life Cycle

0
Filed under Corporate Culture, Developing Teams, Growth & Development

robp

Discover SharePoint

0
Filed under SharePoint

For an introduction to SharePoint, the videos, pages and documents at DiscoverSharePoint.com provide some excellent information.  It is a great starting point for end users and anyone new to SharePoint to go to to discover some of the primary features of and SharePoint and how it can make their jobs easier.

Read More »

robp

SharePoint 2013 Filter By and Display "Start Time" in Content Query Web Part

0
Filed under SharePoint

My SharePoint project requirements were to show calendar items on a site home page in a list format filtered to show only the future events (Start Time greater than today). I have a calendar list with items that use a custom content type where the parent content type is Event.

I added a SharePoint Content Query Web Part (CQWP) to the home page and started to configure it.

I wanted to set the Source to be “Show items from the following list”, but when I selected this, the “Start Time” column is not displayed in the “Additional Filters” dropdown. What’s up SharePoint?

Read More »

paulg

Culture Eats Strategy for Breakfast

0
Filed under Corporate Culture, Developing Teams

Culture is the attitudes, the expectations, and the relationships that define a community. Culture is human inertia in its living form, something that you cannot directly control, but it is very real, very substantial, and often more powerful than any corporate strategy you can narrate.

I’m thinking of a personal example when I was managing a recreational dragon boat paddling team some years back. Some of the core members were interested in moving to a higher level of performance, but felt that most of the crew was interested in beer-league level of play. After much discussion, the informal leaders within the crew decided that we should implement performance metrics, and actually use scientific measures on the ergometer and time trials on the individual outrigger hulls.

Read More »

paulg

The Five Dysfunctions of a Team

0
Filed under Corporate Culture, Developing Teams

Patrick Lencioni is a consultant with some sage thoughts on group performance. Patrick suggests that there are 5 dysfunctions that are common to project teams and sports clubs:

1) Absence of Trust.
2) Fear of Conflict.
3) Lack of Commitment.
4) Avoidance of Accountability.
5) Inattentiveness to Results.

Sound familiar? Join us after the cut for more details…

Read More »

paulg

Einstein’s Riddle.

0
Filed under Corporate Culture

This riddle involves the same thinking as playing Sudoku. There are no tricks, just pure logic and process of elimination. Good luck, and don’t give up!

The riddle:  5 neighbours each have different tastes in drinks, pets, cigarettes, and housepaint. Each neighbour is of a different nationality. Which neighbour prefers to drink water, and which neighbour owns the zebra pet?

This riddle’s origin is attributed to Albert Einstein.  It is believed that only 2% of the population is able to logically solve this without using pen and paper (or searching Google).

  1. There are five houses all in row.
  2. The Englishman lives in the red house.
  3. The Spaniard owns the dog.
  4. Coffee is drunk in the green house.
  5. The Ukrainian drinks tea.

Read More »

roberta

You Don’t Need a Methodology. You Need a Toolkit.

0
Filed under Corporate Culture, Growth & Development

Now, before anyone starts typing an angry response, let me say up front that methodologies are fantastic tools. Unfortunately, they are just that, tools. Just like a mechanic cannot fix your car using a single monkey wrench, a Business Analyst cannot effectively perform their job with nothing but methodologies. I have seen an increasing trend in the IT industry that is putting more focus on methodologies. And what’s the problem with this, you ask? They sound great in marketing materials. You can add fancy and colourful graphics that show how a project or task will theoretically proceed. They can be described as “robust”, “comprehensive”, or whatever other buzzword you want to use. In short, they look great on paper and can be very appealing to potential clients. However, as Business Analysts, we are selling ourselves, our chosen profession and our clients short if we rely on nothing other than methodologies.

I encourage you to take stock of what you have in your toolkit. It should contain all of the skills, resources and knowledge that you use to perform your job. This is where the true power of the “toolkit” analogy lies. By putting all of your skills and resources in the context of being a tool, you are forced to identify if you are proficient or weak in the use of that tool. Now, put your toolkit together. Throw your communication, facilitation and documentation abilities in there. Put more specific skills like strategic planning, data design, graphic design in there too, if they’re applicable to you. And yes, put your methodologies in there, they are after all a resource that you use. As you are building your toolkit, keep track of anything that you feel weak at, so you can work on developing those skills.

As Business Analysts, every project or task that we work on will have its own unique attributes and nuances. Those differences may arise due to the nature of the people we are working with, the technologies we’re using, the environment we find ourselves in or the structure of the team we’re on. This is likely not news to anyone, but the key here is that every situation is unique, and it is exactly this uniqueness that makes it impossible to have a “one size fits all” methodology. Go ahead and use a methodology that fits the project you’re working on, but even more importantly, use your skills and knowledge to deliver the outcomes you are responsible for. Remember that the goal of a project is not to successfully complete the steps of a methodology, but rather to deliver value to the stakeholders.

Going forward, let’s refocus on delivering value with the best tools we have. What’s in your toolkit?

Copyright 2014 by Quercus Solutions