Showing posts with label PMTips. Show all posts
Showing posts with label PMTips. Show all posts
Tools: how to hire / how to interview well
11:08
Posted by jason tratch
We are always assessing potential team members, or we are being assessed ourselves..... in relation to the work-world and personal-world.
Interviews are done formally and informally all the time. If you have a key set of questions to ask, or a key set of responses to provide, then you will have a higher probability of a strong "fit" (always go for a win-win).
Often we think that when we have an internal work related project, we are forced to take the resources available. However based on the project priority, do not be afraid to fight for the top resources and select the best team for the project.
When hiring or interviewing or putting teams together, at a minimum, two basic categories must be addressed:
1) Technical Strengths
2) Personal Strengths
The first part is generally quite easy, and ideally you have a very knowledgeable person or have a set of process-workflow/mind-map questions. Examples include:
1) what methodologies do you follow
2) what templates and tools have you created since you first started to work, how has it evolved
3) what systems do you follow for project work vs operational work
4) what framework have you worked with or support when integrating people, process and technology
5) what organizational design concepts have you worked with and which do you like most
6) what resources do you leverage for support in project work
7) what type of project offices have you worked with and explain a typical project approach
8) describe the product/technology from your perspective
The second part is much more difficult and will have a much higher level of variance based on the culture and environment. This is becoming more important for managing work and/or projects and essentially must have a formal approach in order to ensure success.
Below is a sample of key questions related to an article by Dr. Vicki Holmes. These are items that you may want to talk to and emphasize how they are managed:
1) Resilience
2) Rational Thinking
3) Seeking Support (personal & work)
4) Cultivate Diversity
5) Personal Fitness
6) Continual Development of Gratitude
7) Identification and Communication of Feelings
8) Practicing Mindfulness
The 8 points above were discussed in a different context for the article that Dr. Homes discussed. However, these 8 points can also be an invaluable road map for interviewers, interviewees or basically for a personal professional career/development plan (how can you track growth and what areas can you conduct a personal "check-point" on in order to a) map, b) track, c) analyze, d) optimize/adapt and e) trend/forecast.
PS: A growing movement of project management is to learn how to take more "subjective tools" and put them into a structured approach with more formality, whereby you can treat them with as more "tangible" items.
Tools: Project Teams Need 3 Things
07:25
Posted by jason tratch
3 things that greatly impact how well your team performs include:
1. Belonging
2. Significance
3. Boundaries
Then have a formal plan (include within the project plan and manage it like a deliverable) to help integrate those three
things to form the basis of your Project Culture. Finally, overlay that culture to continuously be Goal Oriented.
1. Belonging
Can be described as knowing where they fit within
the team and also organization. Both
are critical and will overlap, so one easy way to understand if there is an
issue is to ask the question out-right…. “how are you feeling in terms of
comfort and security with your overall position within the project and the company”. If this is not positive, you also need to have a strategy to address it as best you can (since likely you will not
have the time or the resources available – so be creative and let them know you will do your best)
Other aspects of belonging include understanding how each
team member is connected to others, every person wants to fit in and have
positive interactions and attention and this leads to trust, which leads to
strong communication/interaction and thus productivity & performance.
2. Significance
Can be described as the ability to have each
stakeholder understand how their capabilities are aligned with the project
demands. How can the project leadership
team enable all team members to make a difference in the project through
meaningful contributions – providing a sense of personal power. All humans are hard-wired with a need for
personal power and growth of their internal confidence that leads to
independence and essentially self-acutalization. No person wants to be
micro-managed and far too often a manager falls into the trap of:
- Tell a person what to do
- Tell then show a person how to do it
- Monitor the person while they are doing it and constantly
get involved
- Approve/Reject/Criticize then take over near the end
3. Boundaries
Every project has a plan. Although we want each team member to have self-independence and empowerment,
they must be working together and following the same path. We must allow small mistakes to occur and learn from and things will never be perfect and must have paths and culture for optimization. Too often companies establish high levels
rules, policies and excessive administration – which turns employees into
robots. Creativity and innovation are depleted, self pride and accountability become minimized and true value from the employee is lost. It is a fine balance as
to when do you micro-manage and when do you provide freedom to achieve work that you can see was your own and take ownership, pride and self-learnings from.
Tools to enable the 3 parameters include:
Belonging – org chart (diagrams for multiple levels), roles
and responsibilities (customized for each project), RAM (Responsibility and
Assignment Matrix), Communication Plan (swim lanes as to who to go to for what
and when), team building events
Significance – Transparency on Role Accountability and the
assigned person’s Capability (this is key and can leverage concepts fro
Requisite Organizational Design or Elliott Jaques methodologies), check point reviews
(what has been completed – celebrate milestones), recognition culture (do not
need to have tangible awards/gifts we all have a job to do and positive
recognition culture can be instilled into a team without a physical cost to the
project), alignment of project achievements with personal learning or growth
plans
Boundaries – Sponsor’s Vision charter, guidelines, codes of
conduct, plans, objectives, Constraints (money, time, scope, quality, HR), plans, scope statements, requisite organizational design models, work capability models, trust, measurement and monitoring systems, stop or red/yellow/green or go/no-go systems, informal reporting systems (simple/fast social media style updates), trust
Goal Oriented
All of this then must be combined
under a project culture that is Goal Oriented, tools that can help with that include: org design clarity (charts/structure), communication and accountability swim lanes, milestone visuals, bar charts (gannt charts), graphs,
spreadsheets, KPIs, CSFs, objectives, deliverables (ideally you can
have both tangible, concrete goals but do not forget to include the intangible,
subjective goals) and also the excerpts from specific documents such as: Concept, Proposal, Charter, Scope Statement, Project
Plan, etc.
Thoughts: Get it together with "personal responsibility"
10:59
Posted by jason tratch
Read a blog where this guy has so much energy and passion it is amazing! He also links that energy/passion to a structured approach, thus he is highly successful.
I wanted to share his blog (descriptive words below) and a link to his video.
Brendon Burchard Blog Post...
I wanted to share his blog (descriptive words below) and a link to his video.
Brendon Burchard Blog Post...
Life blooms when we take responsibility for our full human experience. To be personally responsible and self-reliant means we have to get our sh*t together and decide to have command over these five areas:
1. Our Aim. What is our goal, our direction, our purpose? What is it that we are moving toward and organizing our lives to achieve and contribute? These are questions of the motivated and purposeful human.
2. Our Attention. Are the things we continually focus on bringing us joy, success, connection, growth? Or are we being distracted by a bunch of garbage and gossip in life?
3. Our Attitude. The power plant doesn’t have energy, it generates energy. Similarly, we don’t have an attitude, we generate one. When we choose to generate a negative energy and attitude, life is horrible. But when we choose to generate and broadcast a joyous, loving, and positive energy, life opens up to us, people feel something new from us, and our entire life blooms and grows.
4. Our Affections. Are we connecting with those we love and sensing the beauty of this life? The emotional quality and connections we feel in life are also a choice, and we should choose to feel again, to love again, to become passionate and emotionally open, giving, strong and vibrant.
5. Our Actions. Our destiny is dictated by our disciplined actions - what we do each day, the habits we develop, our purposeful efforts. Take no action, have no life, no adventure, no progress. But overcome apathy and fear and get going and soon there is magic and momentum and what we love to call, the charged life.
Link to his video that aligns with this topic:
His video really talks to personal responsibility and self-reliance!
When looking at your project successes and failures look first to yourself :)
Tools: Org Structure Clarity = Success in Project & Business
08:08
Posted by jason tratch
A system rapidly gaining popularity in projects and business is from Elliott Jaques. A Canadian psychoanalyst and organizational psychologist, known for developing the notion of Requisite Organization from his 'Stratified Systems Theory'. (Wikipedia, see Elliott Jaques).
The more I study this, the more I realize how complex people and system interactions are within both business and project environments (you cannot have one without the other - so must link both with common platforms).
He continues to help remind us and clarify organizational structure with statements such as..... To be employed is to have an ongoing contract that holds you accountable for doing work of a given type for a specified number of hours per week in exchange for payment. Your specific tasks within that given work are assigned to you by a person called your manager (or boss or supervisor), who ought to be held accountable for the work you do.
These basic concepts and definitions can be simple, yet they can be sensitive and may lead to people having different understandings. Another reason as to why so many businesses and projects fail. Much stress is due to mis-understanding of roles, accountability and management interaction".
Can an organizational theory help us manage failure and risk (and Stress!!!)?
The requisite organization theory in its entirety is a great tool that can be leveraged. It can be quite complex, but two core insights can be considered, as taken from the article:
The requisite organization theory in its entirety is a great tool that can be leveraged. It can be quite complex, but two core insights can be considered, as taken from the article:
Insight 1
The first, is about potential capability and has to do with an innate quality of human nature: the amount of complexity that we can handle when we make a decision. This is complex to assess and often takes 100s of interviews and training to accurately assess, but is something objective and scientific when compared to most HR methods and practices. One of the simple indicators is the length of time span that the person works on (how long does the job or task take to be completed, is the person working on 1 day, 1 week, 3 month, 1 year, 7 year, 15 year jobs). So thus people can be placed into strata, e.g. levels 1 to 7, based on the type of work they do.
The first, is about potential capability and has to do with an innate quality of human nature: the amount of complexity that we can handle when we make a decision. This is complex to assess and often takes 100s of interviews and training to accurately assess, but is something objective and scientific when compared to most HR methods and practices. One of the simple indicators is the length of time span that the person works on (how long does the job or task take to be completed, is the person working on 1 day, 1 week, 3 month, 1 year, 7 year, 15 year jobs). So thus people can be placed into strata, e.g. levels 1 to 7, based on the type of work they do.
Insight 2
The second is about managerial accountability. Every boss is accountable not just for overseeing subordinates, but for their results. It means that if people who report to you "screw up," you can't blame them. You either have to give them the support and coaching they need, or have the authority to rotate them to other posts, because you will be held responsible. A couple interesting aspects of this, is that a manager can refuse an employee that reports to them (have them moved to another job/position), and also the employee should have a Formalized Review Process (development & future growth) which should be managed by the manager once removed (two levels up) and not by the direct manager.
The second is about managerial accountability. Every boss is accountable not just for overseeing subordinates, but for their results. It means that if people who report to you "screw up," you can't blame them. You either have to give them the support and coaching they need, or have the authority to rotate them to other posts, because you will be held responsible. A couple interesting aspects of this, is that a manager can refuse an employee that reports to them (have them moved to another job/position), and also the employee should have a Formalized Review Process (development & future growth) which should be managed by the manager once removed (two levels up) and not by the direct manager.
Granted, this type of system should have one key thing..... Trust with Positive Intent. In the end, establish that as much as you can, then remember to create a formal plan (roll out plan) as to how you will integrate systems such as Elliott's (as per above). Understanding and balance of Systems and Psychology will always create new opportunities for learnings and less stress and thus keep project management exciting!!!
Tools: "Business" Success in Project & Business Management
13:47
Posted by jason tratch
Project & Business Management have many technical aspects that can easily follow logic. This can also thus be easily learned (business school, conferences, books, memorization).
This leads to many people that understand detailed project methodologies and systems, but don't really know how to link it to Business Success.
They lack understanding in the difference of getting the job done - so you can check off your requirements box VS delivering high performance value that leads to making a business impact.
Many businesses identify and assign project/business goals (quarterly/annually), then go into a zombie type of work mode that focuses on "working hard, putting in time, checking the boxes and then getting a bonus once it gets done" attitude. This gets work done and can be perceived as success, but then so much "is left on the table".
The opportunity is that typical businesses lack clarity on definitions of business value and performance and focus too much on requirements. I also think this can in part be attributed to the fact that projects and business involve people and people sometimes do not follow logic.
Solutions evolve and risk events occur continuously (small, large and are cumulative). People are the greatest influence on risk management and they themselves can be very unpredictable month over month based on many, many variables including:
- things at home,
- personal conflicts,
- lack of trust,
- past history,
- variance in knowledge/skills/experience,
- culture,
- expectations,
- vested interest,
- personal strengths/inhibitors,
- capability performance index,
- etc
This is why so many businesses are turning to smaller, more modular projectized environments. To help get work done try to break down the work and then also the definitions of value/success and performance into smaller, simpler, more manageable pieces. Take shorter term views (temporary with a distinct start and finish) with staged, formal milestones from the very start to very end. Understand there will be uniqueness to the project based on variables of the people and the risks at that given time. Draw upon the past, leverage a common platform from which to work from, but then be agile and open since if a business process is not working, persist, persist, adapt and overcome.
Sample tools include:
1) Intangible Assessment: once you have the requirements, step back and reassess from the higher level (put your CEO hat on) and question the theory side of things, the value definitions, the justifications. Clearly formalize how you define value, success and performance. Then understand a process how to adapt if those definitions start to change as the project gains clarity (so if the project changes, then revisit and adapt the definitions as needed - be realistic).
2) Tool Re-Assessment: re-assess the concrete systems, tools, templates and technical practices, confirm if they are well aligned with both the work and the team, understand the difference between policies, procedures and guidelines (which are which)
3) Org Design Assessment: assess the team in place, do not be afraid to change it, it is nothing personal, tooooo often we do not properly allocate the people to the prioritized work, we set the people into their jobs, then new jobs take who ever is available, ensure the culture is open that people will be moving around based on the business priorities and the fit between the job and the people
4) Milestone Check Points: schedule far in advance (entire project) the milestone checkpoints that focus on critical success factors (CSFs) and have a formalized process to do so. Try to avoid pure gut-feel decisions and utilize graphs to supplement the progress. Some checkpoints may take days to prepare and execute, other checkpoints may take hours. If things are not working to plan, do not be afraid, you need to understand why (not only what) and then understand who are the right people to involve. Often the opportunity for improvement (OFI) is with the people and how they understand and respect the processes and technologies they have available - in order to help everyone achieve "Business Success".
PMTip - If it works great - Do not stop thinking how it can be better!
11:58
Posted by jason tratch
Often if things are going well, or we win, or we achieve our goal/complete the project, we then go into "cruise mode".
We lose our sense of creativity to try new approaches and even more common, we lose our desire to take risk (with risk comes failure, stress and often finger pointing so lets just do the same old thing as long as it works - don't touch/play with it).
After seeing a show about rock climbing, it reminded me how humans have some type of inner desire, to constantly grow.... it is an exciting aspect of our species. But we can always learn to be more comfortable with risk and innovation.
A famous rock climbing site is in the USA, called Nose of El Capitan (Yosemite National Park).
The site was considered one of the top challenges a climber could face. Then, people started to set their focus on it and finally, someone set a new record:
1 - an assisted climb was completed in 45 days (this made the news and he became famous, he dominated the sport and stated how it had to be done)
then, years later,
2 - an assisted climb was completed in 1 day (how is this possible, people could not believe it, again, the climber became famous and legendary... obviously that record will not be broken)
then, years later,
3 - a free climb (no ropes/assistance) was completed in 1 day (now this is making people think differently about the sport, and what people used to think, how is that possible). Also, even more troublesome for some people to wrap their brain around it, is that the climber was a woman (Lynn Hill).
then, years later,
4 - a free climb was completed in 12 hours (wow, what next......)
I was amazed, so many stories are right there in front of us, constantly teaching us about continued growth, learning and advancement. Look at old problems from a new angle, things can always be better.
I had to read more about the sport and the stories and the history, since it is a fairly new sport. It consisted of so many people that went into a new level of thinking, innovation and creativity will lead down paths that the previous project/person had not even considered - and could lead to earth shaking results.
Somehow, people find a way! How do they find a way....... after reading more about the climbers that broke the records, and continue to do so, a few things I believe they all had (tools that they posses to break into new levels of success):
- persistence
- passion
- creativity
- confidence
- collaboration
- discipline
- understanding the important link between physical body and mental mind
- non-judgemental and open
Lynn Hill
On May 9, 1989, she fell during a climb in
Buoux, France; after forgetting to tie a safety rope, she fell 85 ft (25 m)
into a tree, and was knocked unconscious, dislocated her elbow and broke her foot. She had been training hard for the World Cup and had to stop
competing for a few months to recover; she was devastated to miss the first
World Cup in the sport. This is where she could retire and live out her life.
However, only six weeks after her fall, she was
back climbing.http://lynnhillclimbing.com/?page_id=5
PMTip - Is PM Training all the Same? What is Project Management?
22:24
Posted by jason tratch
When someone talks about continuous PM Training - often a Manager/Exec states the company does not need it, since they already did the PM training.
Often I hear PMs telling me, they took a PM training course, but then are not allowed any more. They tend to hear " all PM training is the same, and especially when it leads to certification (e.g. PMP) and thus we don't need more of the same thing".
I fully agree to not duplicate things, but, wow, PM is so diverse, and every few years the profession has major advancements - since it is an enabler of business (which is constantly evolving). One thing for sure, you want success in business, you must be open to creativity, critical thinking, communication, collaboration and the ability to evolve and continue to learn.
PM is an incredibly tough profession. Mostly because everyone can rightfully say that we are all Project Managers and we all do Project Management. Thus we can also technically say we are already doing it so do not need training, or we already know so much we do not have time for more, or there is not enough value to take a class since it is too subjective (not enough immediate, tangible results).
Project Management is extremely diverse, unique, complex full of risk and varies greatly depending on the:
Thus the type of training, or education or coaching/mentoring and delivery approach can also have tremendous variances based on different instructors, methodologies, learning approaches, technologies, experiences, knowledge, tools, certifications, etc.
I like to think if you really wanted to get a few degrees to help master Project Management, in no order of importance, I recommend getting: business, commerce, engineering, psychology, sociology, law, science, drama, physiology, computer science, statistics, math, education, HR, marketing, etc.
So how can we define Project Management then???
Often I hear PMs telling me, they took a PM training course, but then are not allowed any more. They tend to hear " all PM training is the same, and especially when it leads to certification (e.g. PMP) and thus we don't need more of the same thing".
I fully agree to not duplicate things, but, wow, PM is so diverse, and every few years the profession has major advancements - since it is an enabler of business (which is constantly evolving). One thing for sure, you want success in business, you must be open to creativity, critical thinking, communication, collaboration and the ability to evolve and continue to learn.
PM is an incredibly tough profession. Mostly because everyone can rightfully say that we are all Project Managers and we all do Project Management. Thus we can also technically say we are already doing it so do not need training, or we already know so much we do not have time for more, or there is not enough value to take a class since it is too subjective (not enough immediate, tangible results).
Project Management is extremely diverse, unique, complex full of risk and varies greatly depending on the:
- sponsor,
- project manager,
- team,
- risk thresholds,
- stakeholders,
- culture of the organization,
- tools available,
- clarity of success,
- etc, etc, etc.
Thus the type of training, or education or coaching/mentoring and delivery approach can also have tremendous variances based on different instructors, methodologies, learning approaches, technologies, experiences, knowledge, tools, certifications, etc.
I like to think if you really wanted to get a few degrees to help master Project Management, in no order of importance, I recommend getting: business, commerce, engineering, psychology, sociology, law, science, drama, physiology, computer science, statistics, math, education, HR, marketing, etc.
So how can we define Project Management then???
In its essence, PM is a structured approach on how to successfully deliver business.
We must remember, business is fluid and there is no perfect answer as to how to do it (not like math or science). We must always try to apply specific science around it (process and workflow and tools and templates) however one must be adaptable since each scenario will carry a level of uniqueness around it (so can be very different based on the situation) and has subjectivity since it will involve many human interactions and expectations.
Couple more points of interest, included below are definitions of Project Management from leading organizations:
- PMI: Application of knowledge, skills, tools and techniques to project activities to meet the project requirements.
- ISO: Note: now has a PM set of standards called ISO 21500:2012, best definition I found was: Application of methods, tools, techniques and competences to a project, includes the integration of the project life cycle accomplished through processes.
- Prince 2 Definition: Planning, monitoring and control of all aspects of a project and the motivation of all those involved in it to achieve the project objectives on time and to the specified cost, quality and performance.
- Wikipedia: The discipline of carefully projecting or planning, organizing, motivating and controlling resources to achieve specific goals and meet specific success criteria.
- Merriam-Websters Dictionary: believe it or not, this dictionary does not have the word project management defined
Thoughts - Top Traits of PM and Business
15:16
Posted by jason tratch
Understand and incorporate these qualities / skillsets into your work everyday!
Note: They have evolved over the past decade. Long ago, top qualities were all technical, then the focus became systems and communications. More recently, see below a list of the top 6 traits for today's successful business and project manager:
Note: They have evolved over the past decade. Long ago, top qualities were all technical, then the focus became systems and communications. More recently, see below a list of the top 6 traits for today's successful business and project manager:
1) Empathy
Tricky word to understand, becoming integral in the work place,
especially with new generations, every single one of us wants it but the work
place seems slow to adopt it (until now), merriam-webster defines it as:
- the action of understanding, being aware of, being sensitive to, and vicariously experiencing the feelings, thoughts, and experience of another of either the past or present without having the feelings, thoughts, and experience fully communicated in an objectively explicit manner; also: the capacity for this
In a world where we tend to think of business in terms of the bottom
line and financial metrics, a discussion of the role of empathy in business
seems like an indulgence. But is it really an indulgence, or is it a
marketplace imperative instead? We now
have studies that show how organizations with happy employees, strong
organizational health, empathetic leaders, and maybe even a social mission,
outperform their peers. See a good link
from Forbes on this:
2) Trust
A word we often over-look and take for granted, hard to earn and
easy to lose, merriam-webster defines it as:
- assured reliance on the character, ability, strength, or truth of someone or something, one in which confidence is placed
Success in projects and business unquestionably requires some
willingness to cooperate with and have faith in others. The question is, how
much faith and in whom? When your project budgets, finances and resources are
on the line, how can you do a better job of gauging trustworthiness and thereby
improve your likelihood of success? See
a good article from Harvard Business School below:
3) Communication
A word we humans have a tremendous level of variance in terms of how
we understand what this is and how it should be provided or received (huge risk
around successful delivery), merriam-webster defines it as:
- an act or instance of transmitting, information transmitted or conveyed, a process by which information is exchanged between individuals through a common system of symbols, signs, or behavior; also : exchange of information
The ability to communicate with people at all levels is almost
always named as the most important skill by project managers and team members.
Project leadership calls for clear communication about goals,
responsibility, performance, expectations and feedback. There is a great deal of value placed on
openness and directness. The project leader is also the team's link to the
larger organisation. The leader must have the ability to effectively negotiate and use persuasion when necessary to ensure
the success of the team and project. Through effective communication, project leaders
support individual and team achievements by creating explicit guidelines for
accomplishing results and for the career advancement of team members.
4) Cool Under Pressure
In a perfect world, projects would be delivered on time, under
budget and with no major problems or obstacles to overcome. But we don't live
in a perfect world
This type of skill must be practiced – and that environment is not fun. But you need to create an approach so when it occurs, you become systematic and grow and improve each time. Some good tips include:
- Do a dress rehearsal before the event (if you can predict it, go through it in your mind, prepare and visualize)
- Address most urgent need first (prioritize and attack in sequence)
- Listen (adrenaline will be flowing, people will want to run and shout, slow the pace, get multiple perspectives)
- Know when to take a breather (respect the stress you and others are under)
- Block out the white noise (anything unnecessary must be put to the back burner)
5) Collaboration
A word that we need to see the value that it brings, it is the true
skill that makes our earth move to the next level, merriam-webster defines it
as:
- to work jointly with others or together especially in an intellectual endeavor, to cooperate with or willingly assist an enemy of one's country and especially an occupying force, to cooperate with an agency or instrumentality with which one is not immediately connected
The most successful initiatives are driven by internal collaboration
across organizational divisions as well as partnerships with external
stakeholders to share mutual goals. "The more allies you have, the better," said David London,
senior director for US government relations at eBay, which is the group
responsible for the company's energy policy.
For more tips, see link below:
6) Problem Solver
One of the more traditional traits, still required in the PM field,
can have multiple definitions, Wikipedia defines it as:
- consists of using generic or ad hoc methods, in an orderly manner, for finding solutions to problems. Some of the problem-solving techniques developed and used in artificial intelligence, computer science, engineering, mathematics, medicine, etc. are related to mental problem-solving techniques studied in psychology.
Problem solving and decision-making are important skills for
projects, business and life. Problem-solving often involves decision-making,
and decision-making and there are processes and techniques to improve
decision-making and the quality of decisions.
See link below to learn several techniques that are always helpful:
Challenge yourself to practice these traits every single day?
Tools - Pre-Sales Checklist
21:33
Posted by jason tratch
Do not underestimate "Pre-Sales or Concept" work activities that need to occur before you Initiate a project. The level of formality should be aligned with the Tier Rating of the project.
As discussed, before a project starts, you can set up a foundation (well worth it)..... or set up a mud pit (do not be surprised when that extra level of stress and anxiety appear - and help others understand this too).
PMI does not even do this approach justice. The PMI process groups start with Initiation.
I would like to see the following process groups:
This also helps people understand, business, operations and projects are all in the same family, they need each other and integrate with each other to deliver ultimate value for the client.
In this very first stage, one could leverage a checklist such as below:
As discussed, before a project starts, you can set up a foundation (well worth it)..... or set up a mud pit (do not be surprised when that extra level of stress and anxiety appear - and help others understand this too).
PMI does not even do this approach justice. The PMI process groups start with Initiation.
I would like to see the following process groups:
- Concept/PreSales
- Propsal
- Initiation
- Planning
- Executing
- Monitoring and Control
- Closure
This also helps people understand, business, operations and projects are all in the same family, they need each other and integrate with each other to deliver ultimate value for the client.
In this very first stage, one could leverage a checklist such as below:
ID #
|
Project
Tasks
|
1
|
Confirm key owners, influencers
and recipients
|
2
|
Define Justification (e.g.
market demand, business need, technology, legal, societal, client request,
etc)
|
3
|
Analyze Sales/RFP or other project documents that are associated with
starting a project
|
4
|
Define
very high level resource requirements (money, people, material, equipment,
tools, time, etc)
|
5
|
Identify
possible sources for resources
|
6
|
Confirm
engagement strategy
|
7
|
Analyze
Organizational Design capability and strength associated with potential work
|
8
|
Review project potential with business vision,
mission, mandate, values, strategy, model and objectives
|
9
|
Conduct peer reviews
|
10
|
Complete
Account Plan
|
11
|
Complete Sales Response Strategy and Documentation
|
12
|
Start
Project Proposal or Charter (as per methodology)
|
13
|
Review Key Information accuracy and levels of
risk/source of error
|
14
|
Confirm
Project approach (phased/staged workflow)
|
15
|
Understand negotiation strategies and boundaries
|
16
|
Review
Plans with resources
|
17
|
Refine and Present SOW and PSA
|
18
|
Attain final approval/modifications on formal
documents
|
19
|
Sign
off on SOW, PSA and formal documents
|
20
|
Identify
and begin Project Acceptance Table
|
21
|
Start
a high level (informal) lessons learned / feedback forum
|
22
|
Present
and ensure understanding of project vs operational environments and
approaches to be taken
|
23
|
Temper
the excitement of “wanting it all – or scope creep before we know what we are
even doing” - with the understanding of trade-offs, constraints and
prioritization (support management of expectations)
|
24
|
Enhance
the excitement of new value for the organization
|
25
|
Communicate
project gate closure and move to next stage
|
NOTE:
And of course, assumed it already an integral part of the Pre-Sales/Concept stage, is to ensure the value and the business case work. WE ALWAYS do work for a return in value and the level of probability of success associated with receiving that value is dependent on the risk tolerance of the organization. Ensure that is talked about and very clear, as always right at the start!
Tools - Microsoft Project Steps before Baseline
10:23
Posted by jason tratch
MS Project is not an easy tool, but it creates one of the
best Gannt Chart or Schedule display tools you can get.
People ask for a simple guideline that can be followed to
create a Baseline for the Schedule.
Note: I also recommend following this if you are looking to
track real costs, or levels of "Effort" (as PMI would call it) but in
the MS Project software it is called "Work". One must clearly
understand if you are tracking Calendar Time vs Duration vs Work. Each tells a different story and has their
place.
12 Steps Before Baseline and the Sequence to do it in,
includes:
1) Project Start Date (Project - Project info)
2) Calendar (Project – Change working time)
3) Effort Driven Schedule (File - Options – Schedule)
· New tasks
created (Auto)
· Work is
entered in: (Days)
· Default task
type (Fixed Work)
Note: Duration = Work/Units
(Advanced – Display Options)
· Show Project
summary task
4) Task Entry (Deliverables, Work Packages, Tasks)
5) Activity Sequencing, Dependencies/Linking (FS then SS, FF)
6) Resource Sheet (enter initials)
7) Assign Resources to tasks
8) Assign level of effort (Work)
· Milestones
(zero effort)
9) Level resources, alter resources
10) Verifications
11) Set the baseline
12) Track Actuals and Progress (% work complete)
· % Work
Complete Column
· Bar colours
and styles, bar text
· Critical Path
(View – Highlight)
· Red/Dashed
Status Date (Project - Status Date – right click gridlines)
PMTip - EQ Core Capacities
11:33
Posted by jason tratch
I took an EQ Assessment & continually go
back to it - to continually learn more about myself.
It puts a formal approach and more of a science around how I work with
different types of people under different types of environments. It is never black and white, however, this is essentially a tool that lets me grow in one of the most critical aspects of project management and business (relationships).
Objectives of this assessment were to
self-identify how well one can manage relationships in the midst of uncertainty (and thus this will also include how we manage risk, complexity, conflict and stress).
The assessment talked about 3 key building blocks. By studying and understanding them, one can build tolerance, resilience, and adaptability, and give new capabilities to relate more effectively with others.
The assessment talked about 3 key building blocks. By studying and understanding them, one can build tolerance, resilience, and adaptability, and give new capabilities to relate more effectively with others.
It is so important to realize how
projects are managed today versus in the past. The focus today is so much more on
the "people side" vs the "systems side", and thus must include a focus on both yourself and the external people you interact with.
There are many assessments out there, the three core capacities that were focused on for my assessment included:
There are many assessments out there, the three core capacities that were focused on for my assessment included:
1) Self-Reflection
Self-Reflection is the ability to access
and name our experience, including our feelings, thoughts, wants, intentions,
and body sensations, and the ability to observe our thoughts, feelings, and
behavior in the moment as we participate in life. Having the ability to first experience and name our experience, to
differentiate our experience from others, and to reflect and learn from our
experience is fundamental to emotional intelligence, the very driver of our
capacity to learn and grow. It is key to know one-self.
2) Self-Regulation
Experiencing varying levels of distress and
pain is a natural part of life. This causes us to feel some degree of
disequilibrium. Self-soothing is the capacity to experience our distress and
manage it in ways that help us reestablish our equilibrium or balance without
requiring others to change. We all soothe ourselves and our emotions daily in a
variety of positive and negative ways, both alone and in relationship. It is key to measure how we regulate our
emotions.
3) Empathy
Empathy is the ability to identify and analyze what
another person is experiencing and to know what that must be like; to "get
into another person's shoes." Deep empathy also will include an understanding how the other person is feeling. It is key to measure our levels of accuracy and compassion.
For more details, can start by visiting sample websites below of some great people that know this area:
http://www.knollandassociates.ca/programs/
http://learninginaction.com/free-download/
(Note: the link above also has a free download)
http://www.knollandassociates.ca/programs/
http://learninginaction.com/free-download/
(Note: the link above also has a free download)
Subscribe to:
Posts (Atom)