change management

Six Blogs On Release Management

Release management is a systematic structured approach of releasing the product to customer. The product journey that starts from requirement gathering from customer, conceptualization, prototyping,...

Project Management Versus Change Management

Change is generally not welcomed in any system and is treated as problem. Change management is full of obstacles some foreseen and some unforeseen somewhat similar in nature as that of project management. Project manager need to overcome a number of obstacles and hurdles while...

Project Management And Change Agents

Change management takes care of any change in the organization that may or may not be directly connected to project. Change management and improvement initiatives may overlap most of the times. Reason could be the goals being taken to be achieved in any improvement process that...

Project Management And Process Improvement

Organizations initiate improvement processes for many purposes. Improvement process initiatives are like investment. Investments initiatives have various goals – short term goals, mid term goals, and long term goals. Same holds truth for improvement process initiatives...

Identification of Customer Requirements Part IX

In situations when the requirement generator cannot be ignored directly due to his potential say in the management, the role of Product Owner become prime in tackling the situation. Product owner must analyze the situation, prepare a case study and put forth his point that if such...

Think Beyond Project Management

Project Management is not everything related to the management of a project. It is absolutely not the end of the road. If you have a well defined project management methodology (or different methodologies for different project types actually), it never means that just the regular...

Ten Tips To Increase Business Application Usage Part II

5. Drive with a top down approach: If the project command is shared with one of the top management member of customer end, it gives a catalytic thrust to the project progress and becomes a winning note for the product. 6. Don’t pass a stupid message that...

Ten Tips To Increase Business Application Usage Part I

Sometimes business applications die an unnatural death even if the application is built with state-of-the-art technology fulfilling all relevant business requirements. The reason of failure does not lie with the application but the people and processes...

Ten Commandants for Project Manager in Requirements Change Management

Requirements Change management if managed haphazardly may become a disaster for both customer and the product, so it has to be managed very wisely and tactically. And the role of a project manager in this is very crucial. In such a case the role of Project Manager can be sequentially summarized...

Project Manager – A Solid Bridge between Customer and Product Manager

Let us talk about existing software required to be implemented at a new geographical location. Definitely because of a different location there will be certain new requirements plus some changes here and there in the existing built to meet customer specifications. This need to be handled very...

How Requirements evolve during a Software Project?

New requirements or change in existing requirements is an inevitable process in any software project. As a project manager you encounter it during every phase of a project. Some requirements emerge internally by your own team and some come from the customer. Internal requirements result from...

Project Scope – Customer needs to be shown the right path

One of the project managers of an ERP implementation company got himself into a tight corner. He found himself in a tough situation where an already ‘mutually sealed’ project scope asked for one or two new requirements (or changes in the existing functionality) from the client everyday while...

What customer type you are?

One customer type focuses on current requirement, rightly built, with more flexibility towards the business requirements built-in in the database rather than in the code. They believe that if the software meets their current requirements well, the future requirements will be built in at the need of...

Why is Change opposed?

A coder or programmer when told that he is not writing his code, by way of presenting him with a list of bugs, he is being told to CHANGE. A tester when is told by his superior that he lacks business depth for testing the product, he is being told to CHANGE. A project manger when told that he...

If you don’t change with the ‘Change’ you get [ex][change]d

In my June 15 2009 post – “Do’s (+) and Don’ts (X) in Project Management”...

Do’s (+) and Don’ts (X) in Project Management

Ten Reasons of getting into pitfall of leaving a scope of software development at customer site

In the previous post we learnt what all could a software project could lead to in presence of higher scope of software development at customer site during implementation phase. Let us see what all factors are responsible of insufficient requirement gathering during business study phase of a...

How to manage Change Management – in terms of scope of the project

Scope defined and decided upon initially by vendor and customer mutually has a large impact on timeline, progress and success of a project. A change in scope at a later stage may call for a big impact on project schedule and progress. Let us see the roles of vendor and customer respectively in this...

Two aspects in Change Management in Software Project

Change management is a subset of project management. In any software project change is to be managed during the whole cycle of development and implementation. Requirements once specified by customer at the business requirements study phase does not mean that there will be no change in requirements...

Change Management in terms of people – how to manage during a project

Although it can not be avoided in real life scenario and that is why there is a risk plan and risk management to avoid such circumstances. But still a lot can be done to atleast minimize the risk and thereby mitigation. Vendor - Management has to ensure the bare minimum changes (preferably NO...

10 top “Do this if you want blunders!” in Software Development and Software Testing

1. Quality Goals are meant only for Quality Department: No department other than quality (project management, product development, documentation, general management etc.) has to read, understand and learn about the quality goals of the organization. It is only the responsibility of...

10 golden rules for Requirements Based Testing

10. Document with complete and clear requirements is as important as oxygen in the air: Requirements based testing is purely based on the requirements specified by the customer or software sponsor during the business requirements study phase. Documentation of all requirements (user...