Showing posts with label Project Management. Show all posts
Showing posts with label Project Management. Show all posts

Monday, 17 August 2015

Why aren't surveys the best feedback elicitation tool?!

Although the value of surveys cannot be denied, and the stakeholders’ feedback, in general,  is so valuable in improving the service they receive; I am in the habit of volunteering very little time for filling-in surveys!!

Simply for many reasons about the survey itself:
- -          Not my business.
It is not directly contributing to my own business objectives, only indirectly through the service I receive from that service provider.

-  -        Accountability.
In all ways, the service provider is accountable to deliver the service of highest quality based on its experience with its business, not based on the experience I transfer to it.

-    -      Prioritization.
My feedback as an end user to a service provider is voluntary, not explicitly a measured output for my day work, so it is with low priority unless there is a specific reason to change that.

-   -       Time.
It is time consuming, filling the survey is a commitment, which consumes time in context switching from other day activities into opening the survey tool, and reflecting on my past experience to fill-in the answers appropriately. It is not very accurate, in reality, to measure that by the few minutes consumed in checking the radio buttons.

-   -       Fun.
it is boring; it usually lacks any fun. Especially those typical direct expected questions like “Rate your satisfaction with that specific service in the scale A-D”, “Do you think we are doing good in delivering our service A?”


What I would suggest is to vary the tools to obtain the same desired output.

For example:
-  -       Feedback can be much more diverse and innovative through focus groups.
-  -       Highest reliability can be achieved through direct interviews with staff, where the input is based on real stories.
-  -        Much more engagement can be achieved through introducing gamification into the process. 
-  -        Improving the effectiveness of a specific tool might be reached through combining two tools together, such as focus groups and targeted surveys.

Tuesday, 4 August 2015

PRINCE2 Practitioner Exam Time Preparation

Examination Paper:

   --> Scenario Booklet: (1 scenario + possible additional information for specific questions)
   --> Question Booklet:
      (8 questions,
      each contains 10 question lines subdivided into parts,
      each part covers specific syllabus area identified at the beginning of the question)
   --> Answer Booklet

Syllabus:


Area
Themes
Process Groups
Others

1- Business Case
1-
Starting up a project
Initiating a project
Overview
2- Organization
2-
Directing a project
Managing a stage boundary
Closing a project 
Principles
3- Quality
3-
Controlling a stage
Managing product delivery
Tailoring PRINCE2
4- Plans


5- Risk
6- Change
7- Progress
Examined
6 out of 7
2 out of 3
- Not examined
- May be included in other questions

Timing: (2h30)

Activity
Scenario & Overall
Q1
Q2
Q3
Q4
Q5
Q6
Q7
Q8
Tolerance
Minutes
10
15
15
15
15
15
15
15
15
20
Accumulative
0h10
0h25
0h40
0h55
1h10
1h25
1h40
1h55
2h10
2h30

Grading:

80 Qs for 80 marks
Pass: 44 marks (55%)


Good luck!



* Some content is based on information from Axelos PRINCE2 Practitioner Examination Candidate Guidance ver 1.12

Wednesday, 29 July 2015

Confused project management terminology: Issue, Off-specification, and Change Request

Issue: A problem that needs either resolution or attention by the project manager.

Off-specification: A project product which has not or forecast-ed not to be delivered as originally base-lined.

Change Request: It is a request for a change to a product from its base-lined form.


For example (Producing a budget laptop):

Issue: Processor specified is no longer in production.

Off-specification: Processor in the final laptop product over-heat.

Change Request: Senior User request a higher frequency processor for the laptop.




N.B. This is within the context for PRINCE2 terminology

Sunday, 28 June 2015

Difference between Business Analyst and Systems Analyst (within the context of the IT)

This is from my own perspective and mainly based on my personal experience:

Business Analyst:
Re-document the business rules and the business processes in a format and terminology that is eligible to be consumed as requirements for introducing new system(s) or redefining an existing business.


Systems Analyst:
Either re-document the exiting system(s) or conclude other systems in an answer to highlight the suitability for fulfilling the defined set of requirements.

Tuesday, 9 June 2015

Difference between Start\Finish times, Baseline Start\Finish times, and Actual Start\Finish times for project tasks.

Baseline Start\Finish times: Those are the planned times entered during planning to specify the planned start\finish times for each task. Once the plan enters execution, this should not change; however, this remains as a baseline (reference) for comparison with the actual Task Start\Finish times for each task for the purposes of monitoring or evaluation.

Actual Start\Finish times: Those are the actual times periodically entered for each task at the head of its execution and following its completion to specify the actual duration for each task.

Start\Finish times: Those are the forecast-ed times periodically updated for planned tasks to reflect any new inputs which are excepted to change the schedule and which were not foreseen at initial project planning.



Sunday, 26 April 2015

Microsoft Project Printing Gantt Chart without Tasks Table

The key here is to hide the Tasks table :)

View Menu --> Tables --> More Tables --> New --> No Info Table with ID column of 0 width.





Then you can print freely, where the Tasks table will not be present.

To show again the default tasks table:

View Menu --> Tables -->

Thursday, 26 March 2015

PMO Tools: Stakeholders Analysis Matrix

Stakeholders Analysis Matrix is one of the very effective tools which can be used to support the classification activity for the stakeholders.

According to PMBOK; Identify Stakeholders is an Initiation process group activity for a typical project management process. It is also the first activity within the Project Communications Management Plan establishment.

Herein, I do define from my own perspective a simple matrix which can be utilized for that same purpose:


Stakeholders Analysis Matrix
Stakeholders Analysis Matrix


Based on this classification, all the communications plan components can be aligned to the goals and objectives for each stakeholders group; hence the channels, the messages, ..etc.

It is worth mentioning that this matrix can be organized from different perspectives. Here, I have tried to present a very simple approach which can be much more elaborated upon according to the project size and the number of stakeholders involved.

Thursday, 12 March 2015

English Language Tip: Fortnight

It is an old English term used as a unit of time equals 14 days or 2 weeks.


Just a note to be careful because it is sometimes used in business referring to salaries, pay periods, social security benefits, or during task scheduling activities. 

Wednesday, 24 September 2014

Three reasons can render you idle in your busiest days!

There are always some periods through our workdays when we are so overwhelmed to the extent that we are literally paralyzed. This is the situation when we are unable to progress in any of the areas where we should be exerting more effort.

Stress can be one of the biggest factors that disseminates the negative energy within our whole beings. So many projects, inefficient communication and un-prioritized task lists are among the very common sources

Shortage of resources such as having a shortage in funding for your projects or the man power for implementing the actual work can be the second reason. When there are so many opportunities; however, for each one, there is always that small piece which is missing. Moreover, this can take the other form when you are so busy doing operational work to the extend that you cannot plan any reasonable schedule for a very promising project staying out there in your queue.

So little resilience in making your choices is apparently another good reason. This is to a great extent coupled with a micro manager who dictates not only the task but also the method to do the task, and expecting that the outcome would be at least coinciding with what she expects. This scenario can result in being unable to proceed or deliver due to the least missing details within the implementation strategy previously communicated. The focus here is on following the steps rather than delivering the outcome and the outcome is assumed to be a guaranteed fruit for the steps performed.

Wednesday, 20 November 2013

Business Tip: Ask rather than criticize!

This is based on professional experience in different situations, and this is especially true when on meetings which involves more than you and the other side. Although, even some managers are very self-confident or at this point, you can say they are totally stubborn about their own ideas. The defensive systems for those personalities are so easily triggered by the least of a criticism for their actions.

The proposed solution I approached for working around this challenge while maintain the liberty of my ideas is to prepare questions which externally interrogates the details, and the consequences of a decision, and internally challenges the success and the validity of the core idea. I know that looks confusing at first; however, by comparison to the straightforward method of revealing your point of directly reveal the points of criticism, you will discover that it deserves the effort.

During one of our staff meetings for one of my employers, staff at different levels were invited to get buy-in for a new project to be implemented. The project itself looks appealing, and the CSF (Critical Success Factors) were neatly presented; however, it lacks a very important aspect of laying out a baseline for several metrics to be able to later on measure its success. This same point got my attention as well as another colleague, who had an earlier opportunity than me to take the floor. He started his words by interrogating about the current state before the project implementation and how this project might not introduce a value at all. Of course, the manager was surprised with the question and she pointed him to the clear project objectives and started over listing the benefits for this project. On my turn, I started by valuing the CSF and showed my interest to have an overview about the current baseline and the other metrics which are in place to make sure that this project is going towards success. The manager gratefully welcomed my questions and she reworded it in her own words, then asked her assistant to note it. Although I did not get an answer up till now, but I succeed in the first place to draw the attention of everyone to the value of my point, without at the same time challenging the efforts this manager and other  stakeholders are putting in this project.

Thursday, 27 June 2013

Success Story: Software upgrade with no business disruption!

Business Case:
- Obsolete S\W product that requires maintenance\upgrade to maintain business efficiency.

Requirements:
- New reporting requirements which could not be easily developed within the old system. (High Priority)
- New bug fixes and requirements which could not be easily developed within the old system. (Medium\Low Priority)

Challenges:
- All existing data to be maintained.
- All existing data to be migrated as the seed for the data in the new system.
- Insufficient resources to build\purchase a new replacement.

Solution Workaround, short term:
- Reports developed directly from the old DB and delivered to the business unit.

(Some time...)

Solution Workaround, Medium term:
- Developing a new DB as an infrastructure for the new system.
- Developing and deploying an integration service to migrate scheduled update from the old to the new DB.
- Developing and deploying the new reports using state-of-the art technology and based on the new DB.

(A year or so here...)

Solution, Long term: 
- Building a new replacement S\W with all the new requirements.
- Depreciating the migration service.
- Depreciating the old S\W.

Tuesday, 18 December 2012

PDUs for maintaining PMP credentials

For me, my best are:
1- PMI Webinars.
2- Working as a practitioner within the profession.
3- Self learning through reading PMI publications.
4- Voluntary work with the PMI CoP(Community of Practice)


Good link from Intel:
"How to Progressively Obtain PDU’s For Your Maintaining Your PMP Credential" by Jeff Hodgkinson




Wednesday, 5 September 2012

Indicators for success as a project manager

Externally: Customer Satisfaction.

Internally: Compliance to Scope, time, cost and quality

Wednesday, 29 August 2012

No! Don't accept responsibility without authority

That's actually, one of the highest risk decisions:

Taking a responsibility to deliver a project which involves resources  whom\which you have no official control upon. At time, you can consider yourself working on good will basis! Good luck!

Thursday, 16 August 2012

Disseminating accountability among sub-ordinates

1) Give them the responsibility.
2) Define the task.
3) Speak it out.
4) Guidance and mentoring on request.

5) Transparent evaluation: Specific performance and attitude resulted in judged outcomes
6) Share finals: Success\Failure

7) Patience: The above steps are not once and for all, they are iterative per task!