The pressure for greater agility in project management approaches increases the challenge of achieving coherence between the WBS and the schedule network. This article elaborates on best practices where the goal of full coherence between the WBS and schedule network can be taken for granted and maintained without effort by the project planner.
Find answers to these questions and more in this Agile Practice Area. If you are new to Agile, take advantage of the resources below and don't be shy about commenting or asking questions. If you're a seasoned pro, help others out and become an influencer. We welcome contributions from all sources and the more you participate, the more visible you become. Let us help you move down the road from "giver of sage advice" to "Thought Leader".
We've gotten really good at standing up and scaling Agile delivery teams, but now many leaders are realizing the challenge is with the upfront 'Discovery' process and making sure the teams are working on the right deliverables.
As Agile and agile thinking has continued to gain traction in organizations beyond the software development teams, project managers are left wondering what it all means to them. Some Agile practitioners promote the idea the PMs are no longer needed once you make the transition to using a practice such as Scrum. Does this mean that the PM role will become obsolete in Agile organizations? Or does it mean that the role of traditional project manager needs to transform to being a agile project leader? If you are a PM in an organization making the transition to Agile, come find out what it means to you and what you need to do start the transformation to becoming an Agile Project Leader.
This webinar will discuss recent data examining whether agile methodologies are more successful than traditional methodologies. Attendees will learn which aspects of agile has led to successful outcomes.
This webinar will consider how the combination of innovation and agility can produce business value while aligning service. Attendees will learn how they can drive change for innovative and disruptive transformation.
The idea is to explore all the project management methodologies in the market - waterfall, agile and lean methodology. We will talk about the strengths and weakness of each methodology in a systems implementation and how to exploit the strengths to ensure a successful project.
by Doug DeCarlo, Principal, The Doug DeCarlo Group
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.
by Doug DeCarlo, Principal, The Doug DeCarlo Group
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.
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.
Do we have to wait until after the project is delivered and handed over to operations to see if it was a good investment? This article will provide practical advice and a proven user research process you can use today to improve your benefits realization management .
The iterative nature of agile development poses key challenges when validating software for regulated industries. With thoughtful planning and careful execution, it is possible to achieve compliance through automated testing. Successful practices using automated validation testing and the steps a team can take to reduce validation cost and time at the end of a release cycle are discussed.
Although the RAG system (Red-Amber-Green) is still widely used in conventional project management as the method of rating issues or reporting on status, it is not only inaccurate, it is also counterproductive. There are agile reporting practices that are much more reliable.
Process is a word often used by many team members when justifying the need to do something that they would rather not do. The cause for this conundrum is not with the process as a concept; the problem is with the decision to force a predefined process on everyone.
It’s rare to read about product development processes these days without mention of the benefits of using agile methodologies, yet one might be led to believe this only works for software development. Are hardware teams left out of the agile world? Not at all. You just need to be agile and adapt.
The discipline of project management tends to be relatively stable as processes and methodologies are well established. However, just as technology and business models change, project management adapts over time. Here are some trends within our industry that are likely to gain momentum over the coming year.
This is the fourth and final installment in this series on using the latest UX methods for focusing on the right problems and slashing requirements-based risks. In this installment, we will be validating designs, using our prototypes for conducting usability tests.
Our webinar Agility, Innovation, Business Value Amplification From How to WOW considered how the combination of innovation and agility can produce business value while aligning service. Attendees learned how they can drive change for innovative and disruptive transformation. Here, the presenter continues the conversation with this Q&A session.
What is UX, and why should you pay attention? In the first article, we looked at the seven key UX activities involved in collecting accurate insights, modelling and validating our designs. Part 2 focused exclusively on the key differences of modern user research methods from traditional requirements-gathering activities. Now we look at building prototypes that will make it easy for us to later validate our solutions with usability testing.