Today, roles have changed. As a project manager, you must keep your projects (and developers) on the right track. It doesn’t matter how many languages or platforms you know. This seasoned practitioner explores two different approaches and applies them to a complex IT scenario, looking at the best of both worlds.
Connect In Person
Advance your BA skills. Earn PDUs and more—all for free. Don’t miss the most popular Business Analysis event of the year! Over 13,000 attend. Registration is FREE. We’re sharing career journeys and talking about the hottest BA and agile BA topics. Register now to attend the only event designed with your future in mind to help you get ahead.
Is Your Agile Transformation Set up to Fail? Find out at the PMI® Organizational Agility Conference 2016, FREE and Exclusive for PMI Members. We know there are barriers that slow your organization’s ability to be agile: failed agile transformations, complex organizational processes, team dynamics and the uncertain role of the PMO in an agile environment (just to name a few). Attend the PMI Organizational Agility Conference 2016 to get help breaking down these barriers. It’s free for PMI Members.
Overwhelmed by how technology is transforming project management? Looking to increase your productivity and learn new tech tools but don't know where to begin? No matter what your focus—medical, manufacturing, product design or otherwise—this virtual day of learning will deliver years of enduring value, with exclusive insights on how project managers are using new technologies. Register today!
This is the final session in our six-part How to Be a Project Hero series. In this session we will discuss how to bring all the pieces together in a LEAN plan and share some techniques on tracking against that plan.
Product management is often a murky role: poorly understood and inconsistently practiced across tech companies – and often confused with program and project management. Yet done well, product management is a driver of market success and effective development.
The journey to Adaptive and Servant Leadership is a long one, it doesn't happen over night and it takes conscious effort to get there. I want to share some of the best tips we've learned from the real world on how to navigate this journey and help others do the same.
Larry Cooper recently approached a group of senior leaders from a broad spectrum of industries, sectors and countries to participate in a Wisdom Council to answer a series of questions on Organizational Agility. In the webinar Larry will share the insights he gathered from them.
Through this session, we'll dig deeper into this subject and share new modern and Agile ways for thinking about performance management for organizations scaling Agile adoption.
In case you actually read this description, the beginning of the blog is about preparing for the PMP exam. It then evolved into maintaining my credential. After taking a break for a few years, I'm back and will be blogging about project management, in general, and probably a bit of agile on a regular basis.
Save Time With Tools + Templates
The Risk Management Grid is a technique to identify potential risk events that could impact one of more of the project’s Seven Win Conditions. Importantly, it also serves to decide how those events will be prevented or mitigated.
The Three-Sentence Project Skinny is a concise summary of the purpose of the project. It addresses the what and the why.
You can't do everything, nor should you. This template helps you figure out what is in and what is out of your project.
These are the do-or-die, must-meet requirements in order for the project to be considered a success. As such, they are continuously focused on by the project manager and core team.
Win Conditions address how success will be measured. How do you stack up when it comes to stakeholder satisfaction, your schedule, scope, quality, budget, ROI and team satisfaction? This template helps you rank priorities, and provides areas for metrics and descriptions.
Learn From Others
When companies move to an agile Software Development Lifecycle (SDLC), they often remove the processes and analysis of their waterfall SDLC because, as the Agile Manifesto puts it, “They value individual and interactions over processes and tools.” Some of the rigor should be removed – waterfall processes can get bogged down with gates and sign-offs. However, caution must be exercised to not go too far against processes and analysis and rely just upon backlogs and user stories. Requirements and the analysis that leads to those requirements are just as essential in an agile project as they are in a waterfall project. The difference lies in how much requirements analysis is completed and the timing of it.
For many, the concepts of agile are distinctly related to software development. But there has been a trend over the past 15 years of agile approaches taking root outside of software development and systems integration projects. Agile has not only appeared outside of its usual places, it has thrived in many of these new areas.
This fourth installment of articles scrutinizing agile frameworks based on values, principles and practices focuses on commitment (following the entries on courage, focus and openness). A stated value of the Scrum framework, commitment is everything in agile.
What does “scaling agile” mean to you? There are two ways to think about scaling: one is moving from one project to a program, the other is sharing agile across the business. Here we talk about moving from a one-team project to agile programs.
This series provides valuable information for the product owner community to use additional good practices in their projects. In each installment, we take one of the most commonly used visual models in agile and explain how to create one--and how to use one to help build, groom or elaborate your agile backlog. This entry looks at the feature tree.
Many organizations are obsessed with getting things done quickly no matter what. Therefore, they create reward plans that motivate this behavior. ScrumMasters gradually deprioritize promoting Scrum values and metamorphose into agile project managers. How can we prevent this?
Most organizations struggle to engage their workforce to its potential. This is not through a lack of planning, technical skills or resources, but instead effective tools for dealing with typical project problems. Fortunately, agile practices hold many practical solutions for solving the classic five dysfunctions of a team.
Today’s project delivery environment is more complex than ever—more projects, more complex projects and more varied projects than ever before. Does this environment still lend itself to a single methodology? And if not, what should an organization’s approach be?
All agile frameworks may be examined in terms of core values. This third entry in a five-part series continues to explore agile frameworks from the vantage point of values, principles and practices. Agile’s Scrum framework in particular espouses five values: courage, focus, openness, respect and commitment. This offering looks at the value of openness to bring principles and practices into better relief.
This series provides valuable information for the product owner community to use additional good practices in their projects. In each installment, we take one of the most commonly used visual models in agile and explain how to create one—and how to use one to help build, groom or elaborate your agile backlog. The first in this series is the process flow.
Do you know what expertise you need now, as you enter into an agile development environment? Unfortunately, we use the same word (“testing”) in agile, but it means something different from what you have seen and managed in prior non-agile projects. If your testers are writing test cases, tracking testing progress and recording bugs in a separate defect tracking system, stop now; you are using the wrong people to do the wrong thing.
|A.||Metrics or concrete, short-term data about the performance of each person working for an organization are crucial to make sure that team members are not slacking off and occupying a position someone else could use to bring the company more value.|
|B.||The new boss is trying to make his or her mark by introducing the new metrics to have something concrete to show. These statistics will prove to not be a good idea over time, so let the organization figure it out for itself. Collecting them is the equivalent of the lion’s roar to mark this territory to all within earshot.|
|C.||Only people who are fearful of what the data will show will object to having it collected, formed into charts and submitted to management. In fact, since you know what is being gathered you can change your daily performance to be sure you look good in these new metrics regardless of whether or not it is the best use of your time.|
|D.||An organization should look at the need for and value received from any metrics gathered and used. Unless they are collecting data that is meaningful and will lead to better results, they are a waste of company time and resources, may be misleading and may be discouraging for the team.|
This is the second in a five-part series of articles regarding agile frameworks based on values, principles and practices. Scrum espouses five values: courage, openness, respect, commitment and focus. In this series, each article will explore one of these values--on which a deeper discussion of principles and practices assembles.
Agile approaches do not have risk management approaches built in as standard; they have the integration points, but not the steps required. Fortunately, with a little effort, we can fill those gaps and equip teams with the skills they need to address risks and opportunities effectively.
|A.||Business analysts replace project managers, so once you assign a BA to a project, your work is over. All you will need to do is help referee the conflicts between the BAs and the IT teams.|
|B.||If your business analysts are trained and certified, they’ll know their own roles or can adjust quickly to what you want them to do. The agile IT team should be fairly self-directed. All you need to understand is who does what, present the responsibility chart and stand back ready to support them if needed.|
|C.||Agile teams do not need any supervision or direction over and above their own ScrumMaster, who is 100% devoted to one project at a time. Ask your BAs if they will cross-train as ScrumMasters to maximize the number of projects you can run at any one time.|
|D.||Due to the new strategic and business requirements from PMI, project managers have now been renamed. Just have your newly christened business analysts do what project managers have always done.|
If you are a traditional project manager practicing agile methods, chances are you don’t really “get” it. Nothing has been worse for the understanding and proper application of agile approaches in organizations today than the flawed thinking and actions of well-meaning middle managers and project managers.
Ask a Question