by Mark Davison
February 10. 2011 16:41
1.
How clear are my instructions?
2.
How open am I to your ideas?
3.
How often do I change direction after you've started working?
4.
How available am I to support or help you?
5.
How do I help you improve your skills and capabilities?
6.
Can you trust me?
7.
Do you respect me?
8.
Do I recognize you for your work?
9.
How organized am I, or am I working in crisis mode?
10.
How well do I run meetings?
by Mark Davison
February 10. 2011 16:40
Smile and be cheerful
Greet others in the hall, ask how they are and what's new
Take extra steps to be nice and courteous
Have a team coffee break
Bring in lunch or breakfast
Share cartoons or jokes (in good taste) with others
Have a special day (i.e., Green Bay Packers day, Wear Your Favorite Team Shirt day, etc.)
Have a contest (i.e., cake baking, barbecue cook off, etc.)
Have an offsite meeting
Have an offsite event (go to the movies, go bowling, etc.)
Award performance with gift certificates and cards (most improved, hardest working, etc.)
by Mark Davison
February 10. 2011 16:39
Volunteer for assignments no one else wants
Let it be known you're here for the duration
Sincerely demonstrate your growing skills, knowledge and expertise
Generate ideas to help the team
Be enthusiastic and make a positive contribution
Ask what you can do to earn your stripes everyday
by Mark Davison
February 8. 2011 14:53
There's nothing wrong with being a “Monday morning quarterback” to take a few lessons in teamwork from the Super Bowl played Sunday evening in Texas. Here are some of the lessons PMs might take to heart.
1. On offense the quarterback is in control. It's his job to call the play, get the ball, then hand off, pass or run the ball to make the play. For those watching Sunday's game, it was clear that both quarterbacks - Ben Roethlisberger and Aaron Rodgers were in command of their offenses when they were on the field. You might think of them as the project managers for each of their teams, each one driving each play (task and activity) toward the goal (milestone).
2. The quarterback needs to be a good communicator. The other players need to hear his plays and be ready to block, run or receive a pass. Similarly, the PM needs to be a good communicator. He needs to be clear about expectations and needs, what the plan is, how to execute it, and assure it gets well executed by selecting the right personnel to perform certain tasks. Plays are designed to take advantage of player strengths. Coaches work hard to design plays to put the right player in the right place at the right time to make the play successful. In Sunday's game we saw this as Aaron Rodgers tossed a 29-yard pass to Jordy Nelson in the first quarter. Nelson was able to leverage his skills in running and catching by pulling slightly ahead of Pittsburgh's cornerback to make a leaping catch for a touchdown. This is a good example of knowing player strengths/weaknesses (on both offense and defense), and how to leverage them into the play. So it is with PMs. As a PM you need to know how to take advantage of the skills, experience and expertise of each “player” on the project team. Your workplan should place each team member in the right role to be successful, and to enable the team to reach its goals.
3. The idea is to score points. Points on the scoreboard measure the success of the football team in the game. For a project, a PM needs to identify the success criteria to measure, then measure them diligently throughout the project. With the right measurements to guide behavior, the project will reach its successful outcome when the measurements are fulfilled.
4. The team “clicks.” When things are going well on the field, the fans can see their football team is “clicking” - that is, passes are completed, runs gain yardage, field goals are made, touchdowns result, etc. Green Bay got “clicking” early, leaping out front for an early lead. The Green Bay fans were thrilled. But in the second quarter, things began to click for Pittsburgh when Ben Roethlisberger combined with receiver Hines Ward on three passes that led to a touchdown, making the score 21-10 at halftime. It's the same with a project team. When the team is really working on all cylinders, team members get along, issue are minimized, milestones are reached on time, deliverables meet expectations for completion, budget goals are achieved, etc.
5. Coaches get feedback during the game. Whether the team is doing well, or not, coaches get tons of feedback. Fans cheer or boo. Observations from the coaching box are fed into game plans. Decisions are made to change players or plays. Defenses are modified. Plans are adjusted to achieve success. As a PM feedback also comes in from lots of sources all the time. Status meetings are conducted. Deliverables are scrutinized. Management provides oversight. Project team members respond to issues and problems. Governance committees provide reviews. Colleagues and mentors offer advice. The PM has plenty of opportunities to revise the project strategy, scope, plan, etc., to address changes in midstream.
by Mark Davison
February 8. 2011 11:12
1.
Define the scope of the review (i.e., based on the phase under review)
2.
Determine preparations so that documents and other deliverables are ready for the review session
3.
Publish the agenda in advance
4.
Agenda contents include:
a.
Brief Background, overview and/or current status
b.
Brief summary of any outstanding issues
c.
Describe the project team that worked on the phase and work completed
d.
Present/discuss any documents/deliverables for review
e.
Explain any changes to the original scope or design since the previous phase, and the impact
f.
Discuss the current performance of key elements in the project such as participation of stakeholders (or not), work processes (working/not working), technology (working/not working)
g.
Review the current project plan, current and future performance, next steps
h.
Discuss contingency plans
i.
Q&A, provide feedback
j.
Stage Gate approval (or not!)
k.
Review and agree upon next steps, assignments, due dates
by Mark Davison
February 7. 2011 12:50
Software one-time pricing
Base license fees
Cost per site
Cost per processor
Cost per device
Concurrent/cost “per seat”
Customizations
Data conversion
Testing
Warranty charges
Taxes
Escrow charges
Legal charges
Other fees
Hardware
Equipment costs
Software costs
Installation/configuration costs
Other components needed to operationalize
Upgrades
Other Software
Network
Third party software
Database
Report Writer
Integration
Operating systems
Training
Materials and manuals
Instructor cost
Facilities cost
Training environment set up
Support and Maintenance
Support Pricing
Help desk
Onsite support
Remote support
Maintenance charges
Annual price increase
Other
Discounts
What currency
Date proposal pricing expires
Usage/transaction fees
Cost of additional licenses
Upgrade fees
Acquisitions/mergers