Viewing Posts by Dmitri Ivanenko PMP ITIL
Project Success: Elements of High Productivity
Categories:
Reflections on the PM Life
Categories: Reflections on the PM Life
| I've been in the project management profession for more than a decade. Admittedly, I've had my share of times when I was less productive than I would like to be. While I haven't figured out an exact formula for having superior productivity at all times, I have noticed what contributes to both success and failure in high productivity, for me. These four elements help me stay on track. Coachability When you are coachable, you can easily adapt. You are willing to learn something new and possibly change something about yourself in terms of how you work, react or approach tasks. Clarity of the overall goal When I'm working on a project, I want to be clear on what we are working on, what the ultimate goal is, or final result that is expected. With the clarity of the goal, it's easier to commit. With clarity, commitment and coachability, you're halfway there. What gets you to the end game is two other elements: discipline and self-control. I'm not perfect at either, but I've noted that when I am most successful, these two elements are present. When I fail or get close to failing, they are lacking. Discipline Discipline allows me to focus on the right activity and to motivate myself to do what needs to be done on a regular basis. While I might be good at "catching up" on what I'm behind on, if I have the self-discipline, most of the time, I'm on task. Self-control Self-control is an act of controlling one's impulses to do something other than the task at hand. I catch myself now getting distracted by some activities, but ultimately, self-control allows me to avoid the wrong ones. We have to remember that what we do is guided by how we think. Every day, I set a goal to have all of these elements in check for any specific project or task. It opens up actions and the things I need to do right away to either stay on track, get back on track or even outperform what was planned. How do you stay productive? Read more from Dmitri. |
Project Management Adds Value to Operational IT Departments
Categories:
Information Technology
Categories: Information Technology
| The structured approach of project management can add value to operational IT departments. What makes this work is the approach that the project management office (PMO) or the project management team defines in its project management methodology for release of the systems into production environments. Operational departments should execute with a process often referred to as "steady state transfer." This process gives the project team the opportunity to validate all the key production processes such as the support, maintenance cycle, systems restore and sanity testing, which is the basic testing of the system functionality. Project teams launch the steady state transfer after successful tests show the systems are ready to be released into the production environment. This validation step -- to ensure that the system processes are well mapped between various support departments -- adds value to the operations teams. The validation step is done during project execution using the steady state transfer process -- and without generating special projects. This validation step in the project management practice guarantees process interface manuals are updated with any changes to the processes and the test results. The operational departments work with the project team to complete this task and thus make a smooth transition into the "steady state" of operation. What processes does your organization use to achieve the same results? See more posts on IT. Read more from Dmitri. |
Rediscover Project Management Knowledge
Categories:
Reflections on the PM Life
Categories: Reflections on the PM Life
| Do you ever notice how after learning a concept many years ago, when you come across it again, you understand it either differently or better? As we experience "life" in project management -- managing various projects, working with new teams and wearing different hats on those teams -- we get to see various aspects of project management in action. We add to that knowledge from our own successes and failures. We usually refer to those experiences as growth and development. The experience alters how we see things and how we communicate with people: our teammates, suppliers, third party partners, customers and clients. It also alters how we perform work because we gain a new point of view or change in our current point of view. As such, it's valuable to review what you already know by reading through chapters of A Guide to Project Management Body of Knowledge (PMBOK® Guide) to focus on the key areas that you work in, be it in risk management, scope management or resource scheduling. When you review the material after having had some experience, you not only remind yourself of what you learned initially, but you see it differently. You catch some elements that you didn't see how to implement before, or you recognize how to relate to something in a way that you didn't before. Having that "life" experience in project management alters how you see the material and how you apply it in everyday work. This happened to me when I reviewed the PMBOK® Guide recently. After reviewing the chapter on risk management, I realized that my company needed to include additional steps for how we handle a backup or restore operation. While many companies have testing strategies, ours only documented this step conceptually. I may not have noticed this if I hadn't reread the PMBOK® Guide. I challenge you to review the knowledge in the PMBOK® Guide and see how you can apply it to your active projects. Areas that you can improve on will turn up and will add value to your project management practice. How do you rediscover your project management knowledge? Have you rediscovered practices from the PMBOK® Guide recently? Editor's note: From 17 February - 20 March 2012, the exposure draft of A Guide to the Project Management Body of Knowledge (PMBOK® Guide) -- Fifth Edition will be open for public review. Find out more and provide your recommendations and comments on the draft. Read more from Dmitri. |
Boost Productivity by Renaming Tasks
Categories:
Project Delivery
Categories: Project Delivery
| Do you assign yourself a task that's actually framed as an expected result? For example, creating or updating a report is a task, while producing a report is a result of that activity. Or, performing a troubleshooting session is a task; solving a problem is an expected result. Language impacts how we work and what we accomplish. This reality is illustrated in project management through the use of the work breakdown structures, for example, where we break down the tasks and label them appropriately to be able to execute them. The work seems easier to accomplish that way. To be productive, tasks need to be executable and controllable. Tasks framed as results are ambiguous because they do not specify an action that can be carried out -- instead, they imply that you will figure out the real action you can do and accomplish. I find that I get a lot more done when I put a task on my calendar that I know I can control. For instance, I can control hosting a meeting, but I can't control the meeting's outcome. Therefore, the task, "Chair a solution review meeting" has more power than "Get the team to approve a solution." When our mind considers a task to be particularly important or ambiguous, it tends to look for an easier outlet or for ways to delay working on that task. It's only when we reword the action in terms that we can understand that we jump to execute the task. The key, I find, is in wording the task as something over which you have actual control. Look at the work you planned for today or the next seven days. Reword your actions and tasks so that you can have complete control over them. Notice what happens to your productivity and report back. Have you seen a productivity boost from renaming tasks? |
Are You a Project Driver or Enabler?
Categories:
Project Delivery
Categories: Project Delivery
| Project managers are tasked with many simultaneous responsibilities. They manage and drive the delivery of a project while managing their team to deliver results according to the business expectations, on time and on budget. It's no small feat when this is accomplished seamlessly. As a project manager, many times I find myself to be the driver, serving as the catalyst for movement and action. A driver is someone who takes on the responsibility and accountability for the project deliverables. So, in addition to day-to-day team management, I drive the alignment of the team to the project plan, maintain quality standards with the delivered work and determine the project execution and communication methods. Enablers act as complements to the driver. They go beyond the task of effectively driving the project activities and focus on the elements that empower the team by fostering a strong work ethic, high morale, satisfaction, and attaining personal and professional accomplishments. Enablers are very good at working with all the team members -- internal and external to the project and organization -- in such a way that allows everyone on the team to: • Align to the overall goal • Emotionally connect to why the project's overarching goal is important • See their own purpose on the team through their contribution and knowledge • Feel validated for their inputs and recognized for their efforts and outputs Enablers add life and color to the project. They are known as the glue that keeps the team together. An enabler can exist within the project team, and he or she doesn't have to be the project manager. The great value of project managers serving as enablers is that -- when combined with their authority, they are able to drive the project and enable their teams to deliver higher quality projects and longer lasting results. This value is reflected in the quality of the product or service, processes and process adoption rate, plus greater organizational awareness and integration. Are you an enabler or a driver? Do you think it's most beneficial to have the project manager as the driver or the enabler? Why? |





