This site uses cookies to improve your experience. To help us insure we adhere to various privacy regulations, please select your country/region of residence. If you do not select a country, we will assume you are from the United States. Select your Cookie Settings or view our Privacy Policy and Terms of Use.
Cookie Settings
Cookies and similar technologies are used on this website for proper function of the website, for tracking performance analytics and for marketing purposes. We and some of our third-party providers may use cookie data for various purposes. Please review the cookie settings below and choose your preference.
Used for the proper function of the website
Used for monitoring website traffic and interactions
Cookie Settings
Cookies and similar technologies are used on this website for proper function of the website, for tracking performance analytics and for marketing purposes. We and some of our third-party providers may use cookie data for various purposes. Please review the cookie settings below and choose your preference.
Strictly Necessary: Used for the proper function of the website
Performance/Analytics: Used for monitoring website traffic and interactions
How do you lead a post-mortem on your project to learn how to repeat the good stuff and lose the bad stuff? Each project team can develop its post-implementation review process to make it as detailed as needed, but here are some general post-implementation review steps that can be applied to any project.
These new skills are reflected in the new Project Management Institute (PMI) guidelines for certification and professional development units (PDUs) needed to maintain certification, a new triad of skills they’re calling the “Talent Triangle.” So, you’re asked to wear more hats, but you’ve only one head. What do you do?
Your thoughts turn to what you should be doing for your professional development in the months ahead… and there’s a lot of choice. I don’t have the time (or the requirement) to take a certification course, but I’m always prepared to develop the project management competencies I need to succeed. Video (recorded or live) and more.
Did you know that 56% of your project budget might be at risk due to poor communications? One of the most valuable resources in a project is the people (developers, engineers, subject matter experts, etc.) One of the most valuable resources in a project is the people (developers, engineers, subject matter experts, etc.)
How to Manage Underperforming Employees One of the most critical new managers’ challenges is faced when trying to manage employees. Out of which, the even more crucial aspect of the challenge is managing underperforming employees. Managers have to manage their teams and help them grow while keeping them motivated and engaged.
Ruth Pearce knows everything there is to know about motivating your project team. I caught up with Ruth to find out more about how to motivate teams and why it’s something you should be actively doing. Why do you think motivation on project teams is so important? She’s even written the book on it. So how do we do it? Gertman et.
Talking about risk puts you in a better position to do something about them especially, as Mark pointed out, “most of our executives are too far remote from the rest of the team.” That way you can head the problems off before they become bigger issues for you and your team to deal with. link] Why is risk management important?
From the beginning to the end of a project, the project manager and team must plan, execute, and deliver the required products and services while interacting with stakeholders. Projects involve interdependent relationships such as the sponsor and other leaders, the project manager and the project team, and users interacting with the systems.
Without exception, I hear—poor communication. Let’s look at five bad communication habits to avoid and what to do about each. Bill could periodically review the charter with his project team to ensure that the team is aligned with the original intent of the project. We all develop habits, some good and some bad.
Scope creep is the more common term but you might hear both, especially if you are working in software development. Ultimately, it isn’t the project manager coming up with new requirements and asking the team to “just do it”. What’s so bad about scope creep anyway? It takes its toll on team morale.
You’ll learn: What delivery approach is the most common How many project managers have considered leaving the profession Why the top career goal for project managers is not what experienced professionals want How many projects a project manager runs How many people in an average project team What keeps project managers up at night And lots more.
Ruth Pearce knows everything there is to know about motivating your project team. I caught up with Ruth to find out more about how to motivate teams and why it’s something you should be actively doing. Why do you think motivation on project teams is so important? She’s even written the book on it. So how do we do it?
I definitely see many good things happening within our community, and the teams and organizations we work with. But Zombie Scrum is still present in different shapes and forms. In short, I’ll describe how poor facilitation of the Scrum events can cause Zombie Scrum. The team doesn’t even know who their stakeholders are anyhow.
Agile is a way of working that comes from software development. While the roots of incremental development methods of working stem back to the 1950s and into the 1970s, it wasn’t until 2001 that a group of software developers published the Manifesto for Agile Software Development. Agile Tools for Agile Teams.
Teams get sick. Change is an opportunity for your team to work together to figure out how to respond to the change request. Change control not only reinforces your team’s ability to work better together, but the positive effects bleed into overall efficiency. Weather gets in the way. Supply chains break.
Thus, concept development is an important key skill for project managers and all those who want to become one. Competencies for concept development In project management, we generally use a very structured approach to work through a plan according to clear specifications. Information for the project team.
We’re tasked with developing new products, taking them to market, making our systems more efficient and well, so much more. Quality is a very good thing in an end-product, but it can slow you down in development. The Exercise : This one is easy; come up with as many ideas as possible — good and bad. Work in a New Location.
For much of the early 2000’s, large companies would shudder at the thought of operating a team in an agile way. The value derived from holding a retrospective is proportional to the talent of the facilitator, and the intimacy of the team. If the facilitation is poor: it’s going to be a bad meeting.
We challenge leaders, we talk about risk and what might go wrong and we call people out on poor performance through project monitoring and control. Conflict should be a healthy part of any team’s development, and it’ a good way to challenge requirements and ensure that your business case and plans stand up to scrutiny.
And we have a lot of data in project management, so these methods are really helpful, especially when it comes to presenting information to executives , spotting trends, and working out what corrective actions we should take to keep projects on track. SWOT stands for: Strengths Weaknesses Opportunities Threats. Root cause analysis.
And so the meal continued through a mediocre appetizer and on until the main course finally arrived … without Brussels sprouts (the good news) but also without anything in their place as requested (the bad news). Presentation can win the day. Simple Yet Stylish Project Visuals to Impress Your Audience. But it shouldn’t be so.
Nine times out of ten, I hear the answer—poor communication. What happens when poor communication exists? Consequently, individuals misunderstand and make bad assumptions. Here's the bottom line -- poor communication drives projects into an abysmal valley. Heck, your team may even abandon ship. Why is it important?
Or perhaps your team said they had gathered the requirements, but in reality, the team had hastily rushed through the requirement process resulting in rework, missed deadlines, and another blown budget. The project manager should define the approach to requirements development and management. Poor requirements change process.
New Technology : You might be working on a software program that is more advanced than your ability to support or your team hasnt yet developed the skill set to use it properly. Poor Planning: Sometimes its as simple as a lack of planning, which is why planning thoroughly before executing a project is so important.
His response revealed his belief in risk management but a lack of actual application with his teams. I will first present a common reason for poor risk management and then present the positive actions you can take. The plan may require too much or too little process and fail to help the team achieve its objectives.
The Change Formula The Change Formula is a highly practical tool developed over the past decade. He guides readers through applying this understanding to various aspects of life, enabling them to recognise how their minds operate, understand and manage their emotions and thoughts, and develop themselves into the people they aspire to be.
The Scrum Team delivers a valuable, useful, and usable Increment(s) every Sprint. In my view: It could be a "layer of cake team", in that it cannot in and of itself delivery value without dependencies on other "layers" of the cake. Scrum Team members strive for net improvements. Self-managing.
Compile the data and present your strategies, goals and options. SWOT: Strengths, Weaknesses, Opportunities, Threats. The following is a basic outline to follow when starting to develop your business case. Allocate Resources: Decide who will work on what, and then assign team members to those tasks. Document everything.
It’s not a bad practice, but why save it for once a year? There is no time like the present for looking backwards and planning forwards. A software development conference with workshops on the theme of Our Digital Tomorrow. The conference serves developers, team leads, architects and project managers. GOTO Chicago.
Enterprise environmental factors can be defined as conditions that aren’t under the immediate control of the project team. Both being beyond the control of the project team, and even the organization that initiated the project, enterprise environmental factors can affect the outcome of the project, both negatively and positively.
If something bad is going to happen on a project, it’s likely related to time, cost or scope. There are project controls professionals who are responsible to the project manager, but they touch the entire project team. Project Development. Cost estimates are developed into budgets and time estimates become project schedules.
You’ll Get the Project Team You Deserve. Because the uncomfortable truth here is that you get the team that you deserve. This isn’t to say that, if you’re a good person, the universe will reward you with a good team. And if you are bad, then the universe will punish you. So, how do you invest in your team?
We challenge leaders, we talk about risk and what might go wrong and we call people out on poor performance through project monitoring and control. Conflict should be a healthy part of any team’sdevelopment, and it’s a good way to challenge requirements and ensure that your business case and plans stand up to scrutiny.
Then, we will explore how to develop a practical quality management plan. The Cost of Poor Quality First, we may not meet customer's needs and expectations. Fifth, your team's morale may suffer. This is often a result of poor quality requirements. Project managers and teams focus on meeting the customer's needs.
Without one or the other, a business will struggle with weak performance. While seemingly impossible, there are principles that guide operational discipline so that a team can achieve these objectives. It started in 1988 and is presented by the Shingo Institute at Utah State University. Excellence is, however, relative.
Visual Project Management is a process that uses the visualization of the project delivery process to drive team behaviors: to collaborate and effectively manage projects to deliver on time. Rather than look at the project plan, look at what the team is doing. Without clear situational awareness, the team will flounder.
At MeisterLabs we develop intuitive collaboration tools for teams from all parts of the world and in all types of businesses. We spend a lot of time trying to simplify and perfect workflows for our users, and so it was only natural that we would soon look into our own (bad) habits and try to make things more efficient.
. Can scrum be used outside software development? I’ve often worked in cases in non-software where I might have had 10 options that I would consider for the team. If you understand more about the business domain and the technical domain, you understand what the team is doing. Absolutely. . And there is merit in that argument.
It is not defined by how confidently content is presented or how smoothly the session ran. A Scrum Master does not simply tell a product team what to do because that isn't their job (but it is part of it). They enter into a learning engagement with the team which is bi-directional. They examine their assumptions.
It’s giving your clients a poor service and doing a disservice to your team as well. I know a project manager who quit her jobs because she didn’t want to work on initiatives developing weapons. Ethics Tip #6: Don’t Ask Your Team To Do Unpaid Work. This isn’t honest or transparent and you are better than that.
Being able to act as a credible, trusted leader is dependent on you and your team making ethical choices about how you manage and lead the work. The plan can include the principles and guidelines you commit to sticking to as a team that values ethics in communications. Ethics Tip #6: Don’t Ask Your Team To Do Unpaid Work.
Since then, as more people, teams, and organizations have started using Scrum, the framework has grown into the most used method for agile product delivery. Interestingly, the strength of Scrum is also its “weakness”. It merely focuses on ‘the what’ and leaves ‘the how’ to the self-managing ability of the Scrum team.
According to the Scrum guide, Scrum teams typically have 10 or fewer people, including Developers, Scrum Master and Product Owner. But what happens with a Scrum team that includes more than 10 people? What if the Scrum team has 10, 15 even more people? However, the larger the team, the longer all of the events take. .
And, unlike in the physical world, where bad neighborhoods are more clearly demarcated, cyber threats can be like a trojan horse. Audits sound bad. Systems Development: To see if those systems which are under development are being created in compliance with the organization’s standards. What Is an IT Audit?
We organize all of the trending information in your field so you don't have to. Join 100,000+ users and stay up to date on the latest articles your peers are reading.
You know about us, now we want to get to know you!
Let's personalize your content
Let's get even more personalized
We recognize your account from another site in our network, please click 'Send Email' below to continue with verifying your account and setting a password.
Let's personalize your content