The integrative approach to resolving irreconcilable elements and solving functional design problems is what connects the legacy of the Bauhaus school of design to the contemporary practice of design thinking. But what is it? And how can it help with managing innovation projects?
What must we do to bring about a Change initiative as smoothly as possible? Communicate! Communicate! Communicate! How much, and for how long do we do this? Until we get sick and tired of the sound of our own voice – then we take a deep breath and a drink of water and we start all over again. Communication isn’t something that stops and starts; it’s a constant activity before, during and after any Change initiative. This isn’t exactly news. We sort of get this. I can ask any audience in the world to tell me the ‘secret’ to good Change and they repeat back “Communicate, Communicate and Communicate some more!” as if it’s been forcefully injected into their cerebellum. The problem arises when the questioning becomes a bit more detailed, “What exactly should we communicate?” The response to that question is usually either a blank stare or the reasonable recitation of the reporter’s standby; Who, What, Where, When, How and Why. Not a bad start. If we’re writing a news article, then these are good solid questions. The Change Management problem requires all of those, and a few others besides. It’s not that the reporter’s questions are a poor tool; it’s just that they don’t address the peculiar psychology of the Change challenge.
All of us know about business processes. Any business development starts with a process organization. Before starting a new project, we also have clearly defined processes and a clear understanding of these processes. We have these processes groups in each project. We need the system approach for the project execution. Understanding Project Management processes in the context of the organization's business processes is very important. It'll help us apply various Project management methodologies, and their effective combination, as well as it gives the possibility of flexible management. This webinar will show a point of view, answering the following questions. Which business processes are we have in the project? How to effectively integrate the project management processes into the business processes of the organization? What could we do for their evolvement?
Advance Your Career
Mindfulness in Project Management: Harnessing the Power of Awareness for Clarity, Calm, and Cooperation
What does it mean to be ‘Mindful’? How can one apply the practice of Mindfulness to enhance the performance of their project team(s) – and, while we’re at it -- ourselves?
Save Time With Tools + Templates
Behind every successful project is a rock-solid, detailed project plan. This template defines every aspect of your project. The final product can be used to make what you are doing clear to all project stakeholders.
This document is a checklist for assessment of whether a project plan meets an acceptable standard. This standard will vary from company to company, so feel free to tailor this form accordingly to meet your needs.
There is a lot riding on your project's work breakdown structure. Use this worksheet to help you plan the WBS smarter and better.
While actively participating in mentorship during a project with a local design/build firm, this practitioner compiled an overview of the project management process as detailed in PMI’s A Guide to the Project Management Body of Knowledge (PMBOK® Guide). Use this overview with other project managers as a tool to reference in your day-to-day PM activities (as well as share with new project managers).
While there are some subtle differences in closing a project with a party or a wake, a carefully defined checklist will help with either ending to the project. This checklist should be defined early on in the project and communicated to everyone who will have input into the checklist at the end of the project.
Learn From Others
Of of the most significant challenges for PMO leaders is managing relationships across the organization. And as the PMO’s role becomes more and more central to all elements of corporate planning and project delivery, politics inevitably come into play. How do we manage that minefield?
Failure to learn from mistakes--and from each other--can cost organizations dearly. Learning and adapting are hallmarks of good project management and of functioning organizations. Making mistakes is not a problem--it's how we learn.
A few recent events have left this project manager feeling very positive about PMOs--and that’s something that hasn’t happened in quite some time. While we can't yet proclaim PMOs as saviors of organizations, they are now on the journey to success.
Although project managers are often called upon to begin a project immediately, it is important to stop and think critically about the project before getting started. By integrating relevant knowledge before beginning a project you can save time during execution and will have a more complete view to help develop adequate and necessary structure, tools, techniques and guidance to ensure project and organizational success.
Randy Iliff presented the 3 Secrets to Successfully Managing Product Development Programs webinar to the ProjectManagement.com community and provided three secrets to successfully manage product development programs. Randy provided a wealth of information in his presentation. We were not able to get to all of the questions during the live session, but we have included them here.
Application integration is the process of exchanging data between two or more business/application systems. Integration between software applications presents a unique set of challenges. The author describes seven best practices that can be applied to any integration effort, large or small, to improve delivery results.
Why did PMI make Project Integration Management the first knowledge area instead of the last? Doesn’t integration happen when everything else is complete? Read on while we continue our series that shows why getting in physical shape is much like getting ready to write the PMP/CAPM exam...
Using continuous testing, one can immediately detect problems in code — before it’s too late and problems spread. Using a clever combination of tests, tools, and techniques you can tell right away when there’s a problem and it’s easiest to fix. The author uses a case study to illustrate the benefits of continuous integration (CI) and how it leads to better quality control (QC) and quality assurance (QA).
The project manager needs to make sure that integration management is not skipped while all of the other project work is going on. When thinking about how you are going to integrate everything together, the following themes are important to keep in mind.
Custom software development is notoriously difficult to estimate. We start with vague ideas of what we want, expecting to fill in the details later. We’re usually doing something a little different than what we’ve done before, or completely different. How can we act more productively?
Ask a Question