|
Agile Is Cheaper, Right? Kenneth Grant explains whether or not being agile is really as cheap for an organization as its proponents claim it to be. Agile’s relentless focus on business value and just-enough work can help teams identify waste—or poor return on investment (ROI) requirements—and gives them the opportunity to change it or leave it out all together.
|
|
|
On Sumo, Architecture, and Enterprise Agile In order to be successful in the ring, a sumo wrestler needs to maintain a heavy body weight and at the same time be in peak physical condition. Just as these Japanese athletes have to find the right balance through a well thought-out combination of diet and training regimen, software development organizations need a balanced approach to implementing application architecture on agile projects.
|
|
|
Agile and Federal Governance—A Look at Contracts and Earned Value Management Richard Cheng explores whether or not federal governance controls are ready for agile implementations. If the federal government continues to implement agile without losing agile’s fundamental concepts, contractors and the government will grow in their understanding and ability to implement effective projects and deliver value iteratively and incrementally.
|
|
|
Coach New People to Success Johanna Rothman describes a hectic situation involving having to deal with four people and four different projects. The folks involved are in over their heads and Johanna can't even tell if these people are qualified for their job.
|
|
|
For Project Managers, Agile Is About Asking a Different Question Daryl Kulak explains that if we don't ask the right question at the beginning of the project, then no matter how well we answer, it won't be helpful. Perhaps the biggest difference between agile and waterfall is the question being asked. The scope of the project and any judgments of progress are related to this very fundamental question.
|
|
|
Agile vs. Waterfall: The Blue Ocean Explains Why Agile Wins The Blue Ocean Strategy gives important insights regarding how to create new market space in uncontested markets thereby making the competition irrelevant. This strategy can be adopted to explain the significance of agile methodologies as compared to the Waterfall method of software development.
|
|