by Bas de Baar
Every software professional that has been part of more than one project knows for sure: no two projects are the same. Different circumstances make most software projects unique in several aspects. And with different situations come different approaches to handle project life effectively: there are mutliple ways to “do” a project. Different circumstances require different approaches.
Although a project is to a large part defined by the required end results and technology used, the main determining factor of what makes a project different from another is people. The entire process of software project management is strongly stakeholder-driven. It’s their wishes, fears, dreams—their stakes—that determine the course of the project. You have to handle a project to really grasp the impact of people on your endeavor. You have to “live” a project to know the force of political games and power trips. You have to lead a team to deliver a project under time pressures to appreciate the constructive power of motivated people or the destructive power of demotivated team members.
Read the full text of Using Stakeholder Analysis in Software Project Management
by Rob Zanfardino
I know what you are thinking. This is one of those tricks used by writers to catch your attention, as described to you in my last article: The Price is Right. To be completely honest, when I first heard the phrase, “Don’t buy any green bananas”, I did not like the sound of it. However the news turned to the positive and I had a chance to reflect upon my life. This quote served two purposes: The first being to remember to pay my term life insurance premium because I would still need it, and second, it would solve an immediate problem of what to write about in my next article.
This quote was told to me by a medical technician while I was having a medical procedure performed. As you may know most technicians cannot release the results of tests until the doctors have had a chance to review them. Being the examinee on the table, wearing funny robes and exposing my best assets, I wondered if this may be the final curtain call. I thought I would at least show the technician I was somewhat interested in the events taking place, so I tried to extract some information out of her regarding the test results.
Read the full text of "Don't Buy Any Green Bananas!"
by Vladimir I. Voropayev, Yan D. Gelrud
Project implementation process modelling is the main active methodological body of the Project Management discipline [1]. The efficiency of decisions made and the whole functioning of the PM system is determined by the adequacy of models for real processes and their meeting the requirements of project management tasks and goals.
The high degree of complexity and laboriousness of drawing up timing schedules for numerous activities performed by many project members using a great range of resources, strict requirements for the quality of plans, the need for regular control of their fulfilment and adjustment call for the proper methods of solving problems of such sophisticated nature.
Today world market of Project Management Software[11] presents products with network models and methods of scheduling based on the researches of the end of 50th- beginning of 70th [2],[7] with very limited possibilities. At the same time the current mathematical methods of modelling project processes (classical network models [2], generalised [3, 4, 5], probabilistic [6] and stochastic [7] network models) do not always appear adequate to the complex reality of the modelled process. It should be noted that it refers to each method taken separately and to some combinations of these methods.
Read the full text of Cyclic Stochastic Alternative Netwrok Models for Project Management
by Florin Gheorghiu, PMP
Project Management (PM) has now become an extremely fashionable topic for discussion and it seems that this trend will increase even further in the future. The Project Manager as a professional individual has gained sustained and strong credentials throughout the world. Practitioners today are struggling everywhere to keep their standing up and to get nationwide certification from reputed institutions.
Like individuals, organizations tend to adjust and upgrade their behavior for better representation in the market. They are also keen to embrace methodologies, procedures, rules, and tactics in order to become prevailing actors in certain fields of PM application and in the marketplace. There are some major problems, however, with how companies try to implement project management methodologies. This paper discusses three major problems that I have noticed in how organizations implement PM.
Read the full text of Why Companies Fail on the Way to Implementing Project Management Methodolog
by Mark Kozak-Holland
Most people are very familiar with Winston Churchill but may not be familiar with his approach to project management and his PM skills. Parts 1 and 2 introduced the series and how Churchill acquired a project from hell, and why the skills that he brought to the project made him so uniquely qualified. Part 3 looked at his actions up to 1939 that made him a real alternative, and part 4 looked at how technology impacted the Allies “First World War” frame of mind. This article looks at how Churchill acquired the project in May 1940 and took immediate actions, and compares this to the act of project acquisition in today’s world, and the importance of setting expectations.
The May 1940 the U.K. faced a desperate situation as Chamberlain had stalled for peace hoping he could manage his way out without declaring war. The U.K. was hopelessly unprepared for a modern war (Part 4). On May the 8th the British Parliament questioned his handling of the Norwegian campaign with the loss of about 4,000 British troops and the occupation of the country. In a vote of confidence his majority crashed as politicians lost faith in his failed leadership. A “coalition” government was desperately needed but the opposition parties, senior Labour figures, opposed forming this under Chamberlain. They firmly believed that the only leader credible enough to take over was Churchill, and made this a condition.
Read the full text of Churchill the Project Manager (Part 5)
Read the full text of the entire series.
Editorial Policy: The PMFORUM® has no connection to any national or international project management organization nor does it reflect the policy of any project management professional or commercial organization. The PMFORUM® maintains an objective and impartial view of project management affairs. In the interests of advancing professional project management the PMFORUM® will publish contending and objective views on issues that reflect collegial differences and perspectives