The easiest solution is not always the best. It is more effective if you choose the best methodology for each single project based on its nature. Scrum doesn’t fit all projects’ needs. Kanban is another agile methodology that, believe it or not, works more smoothly for at least one type of project. But what type?
As more organizations become agile, clear, real-time communication becomes increasingly important. Here are a few tips to keep in mind to ensure your communication remains effective a new fast-paced environment.
What is the ideal tester-to-developer ratio for the development team? On the surface, this might sound like a perfectly reasonable question—one that should be easy for an experienced practitioner to answer. However, when you look deeper into the question, you will see that it has layers of underlying assumptions—including ones about corporate culture, politics and the likely skills of their own staff.
This real-world example looks at how agile principles were applied to an international company’s global ERP project. It discusses how agile was used to provide continuous feedback into how the project operates. It discusses many of the company’s lessons learned and how it solved challenges in a typical waterfall environment using agile principles.
How should a team calculate realistic velocity? How fast should a team go? The assumption of higher velocity points is a reality in agile projects, and the ability to adjust to the "right" velocity is a challenge posed to every agile team. Quickly adjusting the team velocity with respect to the sprint backlog is critical in accomplishing the delivery of the scope of the planned release.
Question: Whether I’m working on an agile or a waterfall project, we always get an overload of features or activities to complete. In theory, it sounds easy to prioritize them; but in practice, that’s where most of our projects bog down. Defining the order becomes a politely disguised free-for-all. At the end, while we may be able to set up the project, I’m still not convinced that we have made the best long-term choices for the company in our selection of which items we have elected to implement. Is there a fresh way to handle these decisions?
The manager or product owner who pays for the project always has the final vote. Even if you know he or she is missing important viewpoints, you should accept those decisions and work your hardest to make them deliverable. If it goes astray, it’s not your problem.
A business analysis tool, the Purpose Alignment Model, may be a fresh insight for your management and your team into which items on a Scrum Backlog or a project management plan should be prioritized and which should be done with a minimal amount of cost and effort. Try this fresh approach for a new view of your project work.
Rapid application development (RAD), which uses fourth-generation languages and frameworks such as low-code development web applications, is a technique one can use across all industries and on all types of projects. Get a clearer look about the value of each product feature by switching to RAD.
Some purposeful activities in modern corporations are not appropriate for project management techniques. Only governmental and not-for-profit entities can gain value by their use, since the need to get a profit or any return on investment is limited in these types of organizational structures.
What happens when you are not part of an agile development team? If you aren’t exercising your planning rituals and weekly sprints, will you lose muscle memory? Or is there an opportunity to apply what you know to better all aspects of what you do?
Implementing a hybrid methodology can be more effective and useful to your project needs, because traditional approaches can sometimes be too heavy and complex for incremental projects. Here, a practitioner shares his experiences consulting on a project.
Should ScrumMasters ever attend the daily scrum or stand-up meeting? As a guiding principle, agile values self-organizing and self-managing teams, but let’s explore five scenarios where the presence, and perhaps even participation, of a ScrumMaster could be helpful if they adhere to a specific role.
Agile processes can offer rewarding advantages to traditional software development, but they take time to adopt properly. New teams will likely encounter conflicts and confusion during their first sprint retrospective. Here are five lessons learned that can help your next sprint avoid some common pitfalls.
The words “agile project management” are being used in the industry to describe a new approach to how project management is conducted. The industry and company leaders need to fully understand how project managers can be brought into the agile world to ensure cohesion between these two disciplines.
A more nuanced approach to agile and waterfall has started gaining traction. Once referred to as “structured agile,” more practitioners are combining both methodologies. This article provides a framework for how ScrumMasters and project managers can work together using hybrid principles.
The approach to scope changes used within the agile/Scrum framework provides a stable environment so the development team can focus on getting work “done.” Frequent feedback about the product allows for less upfront planning and means the Scrum team can quickly adapt to changes. Delivering business value early and often results in increased customer satisfaction.
Testing at the end of a development cycle is a common practice in traditional approaches. Unfortunately, it becomes an obstacle on your path to agility, slowing down your ability to deploy to production faster. Let’s take a look at what goes on in this testing phase, some potential causes and ideas for getting unstuck.
Is your organization undermining the benefits of Scrum without even knowing it? Scrum is a simple agile framework that can be difficult to implement. Here the author looks at the seven most commonly missed or abused rules of Scrum.
Following installments on the other four stated Scrum values (courage, focus, openness and commitment), this concluding entry focuses on respect. It offers techniques to scrutinize agile project management frameworks based on values, principles and practices.
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.
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?
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.
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 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.
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.
These days, it takes more than project management skills to succeed. It takes a person with agility—flexibility in understanding and applying the ins and outs of any method. Let’s investigate what "hybrid PM" is all about!
"But the fact that some geniuses were laughed at does not imply that all who are laughed at are geniuses. They laughed at Columbus, they laughed at Fulton, they laughed at the Wright brothers. But they also laughed at Bozo the Clown."