The risk we take in swearing allegiance to a specific approach is that following the approach often becomes more important than achieving the goal of the project. Let’s explore the merits of using the best of different approaches—and how marrying them into a hybrid model impacts the way projects are planned and managed.
If you have not run a hybrid project leveraging agile and waterfall methodologies, you are in for a great learning experience. Let’s put the two distinctively different approaches into a broad and high-level context…
As hybrid projects become more common, what has to change among team members, and how do we manage that change? Do we have to minimize these disruption scenarios, or can we create an environment where teams are more comfortable with the shifts?
Question: We have switched to agile practices and, if I do say so myself, I think we are doing an awesome job. However, even though we are carefully creating backlog lists and writing user stories, more often than not our end product or service still does not meet the expectations of our internal and external customers. Has something been left out of what we were taught?
Agile does provide a way to use non-functional requirements in its methodology, but often it is overlooked or not stressed when new teams are preparing their first few projects. Make a point to add them into your new process.
The reason agile projects are completed so much faster and provide so much more value is that with the Scrum practice methodology, it is no longer necessary to consider vague things like non-functional requirements. If they aren’t going to function anyway, why bother with them.
User stories are only written if there is a need for outside personas to be created to represent users. Non-functional requirements are the ones assigned to those personas who would not be interested in your product or service, and therefore can be excluded from consideration.
Many projects have both functional and non-functional requirements that impact the outcome of the project. That is why only traditional processes should be used. Agile processes work only on software projects, and then only when there is an absence of non-functional requirements to be considered.
by Kevin Aguanno, PMP, MAPM, IPMA-B, Cert.APM, CSM, CSP
Trying to implement agile DevOps in a traditional DevOps environment is a huge challenge without first changing underlying governance practices. In this article, the author explains why--and identifies some success factors.
How do the biases, effects, fallacies, illusions and neglects outlined in Kahneman’s Thinking, Fast and Slow (2013) affect decision making? By applying Kahneman to the Knowledge Areas of the PMBOK® Guide, the author illustrates how project managers can mitigate the effects of irrational thinking.
Are command-and-control undertones hurting your organization's performance? Are people getting the passion and desire to contribute slowly crushed out of them by project management bureaucracy and prescriptive process? Then free them to be hyper-productive by emphasizing collaboration.
Some topics in agile testing may point to dysfunctional organizational practices that are often taboo, off limits or avoided in regular conversations. In this article, we identify four such topics that need to be discussed and addressed for agile success.
Companies seeking to cope with the pace of accelerating change are looking for ways to go faster, and managers in non-technical disciplines have become increasingly infatuated with the agile software development methodology. Agility sounds like a good thing, and agile marketing sounds like it must be better than regular marketing...but is it?
The transformation from waterfall to agile frequently meets with resistance to change. Many startups who want to embrace an agile approach fall into a vicious trap of a blended methodology often called “Wagile.” Learn how to encourage development of an agile mindset in your organization.
There’s a simple solution to complex projects: Create agile project teams. These teams close the gap between business areas and IT, reduce the workload, do away with rework and improve communication and team performance.
Agile principles have expanded much further beyond their software development roots. Here, we look at how agile principles were used in each step of the process to make a multimedia invention emerge from inception to reality.
Question: We’re totally committed to agile as a methodology, and we think that is partially why we have now grown so big that we need to open a customer call center. However, my expertise is not in planning contact centers, so what is the current wisdom of how these need to function to satisfy customers?
Customer inquiries are best served by FAQ sites: online and well-written website summations of the products you offer and the way they function. Spend your money in this type of development, which is probably more comfortable for you anyway.
Most staff members are reluctant to move into customer support functions, so you will first need to make sure there are enough competent people who know about your offerings available for hire. Prepare hands-on tests to screen out those who do not already know your merchandise or service products.
Call centers are the most cost efficient way to deal with customer issues, but you should outsource this function as creating your own may be beyond the skill set you possess. Third-party providers are uniformly cheaper than an internal system.
First, determine if it’s in your organization’s best interest to create a call center or a contact center. They are two different things and have different pluses and minuses. Then consider a management style for the center based on the agile philosophy.
In more traditional projects, we often hear about "control." But what might an agile project manager do? Here are three examples of servant leadership in action with respect to the team, the product owner and management.
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.
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.
Are you managing your applications? Is agile everything? What about the cloud? One expert reflects on some of the industry-specific project portfolio management trends of the past year--and considers trends for the coming year that might have an impact on the business.
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.
"He may look like an idiot and talk like an idiot, but don't let that fool you. He really is an idiot."