In today’s fast-paced world, organizational agility is critical to business success. However, it’s common for there to be a clash between the traditional top-down business culture and the agile business philosophy. Agile project management is not just a set of processes and predetermined activities, but rather a genuine philosophy that forces organizations to embrace a brand-new mindset.
Traditional project management and agile project management are two contrasting styles that are often pitted against each other, each with unique values and downfalls. The best methodology to use for a specific project largely depends on the nature of the project and its requirements. Consequently, it’s important to understand the premise of each of these styles and the attributes that differentiate them.
Fixed-price projects are a challenge to manage when using agile practices, as software teams need the flexibility to change what they are building based on customer need, and that often alters what can be done within a fixed budget. However, there are ways to achieve agility even within a fixed-budget constraint. Here are three ways to make a fixed-price project a win for all parties involved.
With traditional software development methods, you are betting that end-of-lifecycle testing will let your team correct all risks, but experience has taught us that this seldom happens. With agile, you are incrementally reducing risk with every iteration and release you do, mitigating risks as you go. This article examines each of the value statements from the Agile Manifesto to illustrate how agile ultimately helps us reduce product risk.
Of all issues that impact getting quality products out on time, the team should never focus on simply managing costs. To minimize the risk of perpetual product delivery delays, define what “done” really means.
We’ve all worked with a talented developer who can be a frustrating challenge to manage. First-time managers may unknowingly encourage bad behavior. There are several innovative ways to resolve the situation.
In this interview, Axosoft evangelist Tania Katan, who is also the creative instigator of the international viral campaign #itwasneveradress, reports on being invited to the White House’s United State of Women Summit. She talks about agile project management, activism, and Michelle Obama and Oprah.
Diane Zajac-Woodie sat down to discuss her upcoming presentation at Agile Development and Better Software Conference West 2014, why the business analyst role doesn't get the attention it deserves, how the BA role can make a difference on agile teams, and her alter ego as the Agile Squirrel.
In this interview, Ellen Gottesdiener talks about her presentation at Agile Development Conference and Better Software Conference West 2014, the importance of having context for requirements, good ways to set value considerations for requirements, and the common mistakes of product owners.
Jeff Dalton is an author, a consultant with more than twenty-five years of software process improvement experience, and president of Broadsword, a management-consulting firm. In this interview, Jeff talks about agile resiliency and large organizations making the agile transition.
Operating on the philosophy that one must thoroughly know the rules before one can break them, a global company developed its own delivery model that is still as true to the agile mindset as is possible. Join Arjay Hinek in this lively session as he deconstructs his company's experiment in melding agile with construction project management to create a hybrid delivery model. At first, the teams were struggling with clear ownership, timely communication, and clear follow-through on work in progress. From modifying the user story mapping model in order to improve project initiation to dissecting and rewriting the values and principles of the Agile Manifesto, Arjay stretched agile practices to the limit to help his teams strive and grow through iterative and incremental delivery. Arjay will share the struggles, failures, and successes of this innovative experiment.
Substantial confusion exists about the roles and responsibilities of test management when using an agile software development process. Agile seeks to streamline project management and leadership under the role of a ScrumMaster, but what does this mean for test managers? How do they stay...
Testing dashboards can give stakeholders the false impression that projects are under control. But are they really? As a tester, you can see a counter indicating a high percentage of passing tests but know that you may still have critical failures in the product. Alexandre Bauduin will...
Imagine this scenario: Business users are excited to finally get their hands on an implementation delivery that is on schedule, (mostly) on budget, and passed rigorous testing with flying colors. Unfortunately, when working with the new app or feature, the users realize that the way they described their needs didn’t translate into what they actually needed. Sound familiar? While she may not be able to offer telekinetic mind-reading tools, Kim Tatum is convinced that leveraging a behavior-driven development (BDD) approach helps bridge the gap between domain experts and technical teams. Join Kim to discuss how natural, human-readable language ultimately creates shared accountability and reduces misunderstandings. Review how this framework is implemented on a variety of delivery projects and walk through an implementation approach and leading practices.