How to overcome from project challenges?

How to overcome from project challenges? - 1) Scope Creep

As a Project manager we face lot of challenges in project, we will discuss Scope Creep and how to overcome from the challenges.

Scope creep:

Project scope is all the of the work that needs to be done to make the product.

This is the big part of what the project manager's are concerned with. This is the work the team has to do.

Scope creep means uncontrolled changes that causes the team to extra work.

Uncontrolled means the change that team is working without bothering about project's time, cost, scope, quality, risk and resource utilization.

Question comes to our mind is why scope changes?

1) Good change

Good change happens rarely in the project, it simplify the way of implementing the requirement and design.

2) Bad change

When you see from outside it' looks good when we start implementing it affects all the criteria mentioned above.

Scope creep is one of the bad change, when we implement one change it leads to new one and it go uncontrollable.

Gold plating is the another type where a developer thinks of a way to make a feature better (without discussing with anyone)

This may sounds good but we have to pay for these features not asked by customer.

We need to use the technique "Control Scope process" to overcome this challenge.

First we need to have the baselined project scope document. If we are following scrum. We need to finalize the Epic's planned for the release.

Project manager need to perform variance analysis against the baselined project scope if any changes coming then he need to follow the CRB process to include part of the requirement and update the project documents including baselined project scope and project plan.

Project manager need to proactively engaging with clients during the project planning phase can help you get their exact requirements as well as understand their expectations.

In addition, planning your resource and talent usage accurately.

It’s also important to not take up ad-hoc change requests during project execution as this can result in delays and added costs. Stick to the initial plan.

Comments

Certified Enterprise Architect Professional (CEAP) - Module 5 - Architecture Frameworks

Architecture Frameworks: An Architecture Framework is a theoretical structure that has the purpose of developing, executing, and maintaining an Enterprise Architecture. Advantages of EA framework: Simplify Breaks down areas of the business process Organise business components and create and identify relationships between business Determine the scope Customization in the existing framework Disadvantages of EA framework: Need to follow process Provides only direction and not information It's based on goal and objective Need creativity and proactive thinking Zachman Framework: The Zachman Framework is a widely used model in Enterprise Architecture (EA) that provides a structured way to classify and organize an organization's information infrastructure by defining different perspectives from various stakeholders, allowing for a holistic view of the enterprise and facilitating alignment between business needs and technology solutions; essentially acting as a template to organize arc...

Daily Agile Scrum stand-up meeting guidelines

Followers of the Scrum method of project management will typically start their day with a " stand-up meeting ". In short, this is a quick daily meeting (30 minutes or less) where the participants share the answers to the three questions with each other: • What did I accomplish yesterday? • What will I do today? • What obstacles are impeding my progress? Some people are talkative and tend to wander off into Story Telling . Some people want to engage in Problem Solving immediately after hearing a problem. Meetings that take too long tend to have low energy and participants not directly related to a long discussion will tend to be distracted. These are the minimum number of questions that satisfy the goals of daily stand-ups. Other topics of discussion (e.g., design discussions, gossip, etc.) should be deferred until after the meeting. Here are few tips for running a smooth daily meeting: • Everyone should literally stand-up and no one should sit down ...

Empiricism (Scrum)

Empiricism asserts that knowledge comes from experience and making decisions based on what is observed. Pillars of Empiricism . Various practices exist to forecast progress, like burn-downs, burn-ups, or cumulative flows. While proven useful, these do not replace the importance of empiricism . In complex environments, what will happen is unknown. Only what has already happened may be used for forward-looking decision making. Each artifact contains a commitment to ensure it provides information that enhances transparency and focus against which progress can be measured: ● For the Product Backlog it is the Product Goal. ● For the Sprint Backlog it is the Sprint Goal. ● For the Increment it is the Definition of Done. These commitments exist to reinforce empiricism . The sum of the Increments is presented at the Sprint Review thus supporting empiricism .

High-Tech Yuga

Search This Blog