Skip to main content

Good, Bad and Ugly Part of Project Management

Project management stories


When it comes to project management, there are definitely many stories with  everyone out there to tell it may be Good, Bad and Ugly, Whatever it may be it  does not matter as far as it is meeting the successful delivery of the  project and said goals and objectives are achieved. But each story will have different colors to tell and how it can be managed, it may be with relationships, infrastructure, stakeholders, execution, resources in terms of cost, scope, operations etc. Readers can classify them as per their appetite.

Make simple things simple:

It is always good to be simple for straight forward task to be done. Always  have to do list in a diary in written it helps a lot. It is always good to track task and status in Spreadsheet. Using a web based Wiki for project can really work based on its availability to users. A wiki can work as single location for processes, planning,  docs, collaborate, communication point, issue logs and tracking.

Try to Make complex scenario/situation simpler

Visualization is key to make things simple. Many a times complex projects requires task breakdown at more granular level than usual to make things simpler. Projects run into bad scenes when task start delaying and getting  accumulated over a period of time. As systems approach says to solve problem of larger context by viewing them in parts and solving problem in context to relation of the parts and then joining these parts together results in synergistic solutions. Systems approach provides modular thought process to disintegrate a complex system into small task and catalyses the whole system.

Projects in critical condition

Success has many fathers but failure is orphan. Projects turn into ugly situation when things go awry and the blame game starts. A pyramid made of blocks can go down at same depth which is it attained height if team members starts pulling legs. One has to think every  project is a mission critical project and same has to be re-iterated again  and again like chants.



All is well that ends well
 
A project manager need not have to reinvent the wheel to handle the scenarios  emerging out of difficult situations. Projects are managed via standard "PMBOK" management process and not rocket science.

Comments

Popular posts from this blog

Usecase Scenario development and User Stories

A common comic mail circulates with this image, which gives good understanding of how requirements captured during a project life cycle goes like this: Typical Software Development Life-cycle explained Above picture succinctly tells about common perception of developing a software, how requirement understanding filters with changing roles, time and space with gaps between factual and results. Thanks to the  the word "agility", which has evolved in world of software technology with the evolution of Rational unified process the term use-case or scenario development for documenting and capturing requirement in the initial phase of software development. "A use case is a software artifact of systems and process of expected sequence of interactions between a module and an external actor, which leads the actor to desired goals and objectives. " Use case scenarios can be mirrored as clip of a movie making scene development where-in director has assigned a s...

Games People Play in context to Projects

Games People Play in context to Projects: Contextually life and projects full of games, work on  dynamics of human relationships by   Dr. Eric Berne guides us not only in many social but relationship situations in corporate world also. In Todays concurrent world where we are living in a global village with Orkut, Facebook, Linkedin, Twitter and other social media leads to discounts of information in social network, where more of transactional games played knowingly(conscious) or unknowingly(unconscious). Precede to this let us understand game, A game full of transactions played with different roles by players changing their roles for a outcome in different ego states like Parent, Adult and Child ego states that will payoff.  Continuing with Payoff, specifically in context to Project teams where transactions happen at concrete or transformational levels where people not necessarily behaving rationally and motivat...

Constructive Blame storming and using Devils Advocate in problem solving and competency development

Cover of Six Thinking Hats Discussions leads to solutions , mistakes leads to innovations, As part of innovation , solution approaches, models quite often used technique in healthy discussions on day to day basis is Brain Storming , mischievously known as blame storming. To the extent organizations build competency around subjects of real time situations, till it takes to materialized very few of them make it to the concrete implementations. Take for example Google revolutionized the way we use internet with countable team, that storm sustained and now second wave coming from Facebook, Linked etc. Questions asked about their revenue models but skepticism will always there, social networks are strong tools not only for marketing but of communication, collaboration, and increased productivity and realized intangible benefits. Discussions are full of Arguments, counter arguments, statements, facts, thesis, anti thesis etc. Contextually the term devil's advocate can be dis...