The Latest
 |
Four Agile Tips to Eliminate Rework in Application Development[article] Your applications need to meet business needs, overcome complex processes, and provide instant results to customers. And, ideally, they’ll require minimal rework on your part. The first step to success is requirements definition. Here, Filip Szymanski offers some tips from agile methods that will improve your requirements—even if you haven’t otherwise adopted agile. |
|
|
How Do I Write Requirements Using Stories and Acceptance Criteria?—Part Two[article] Russell Pannone and Geoffrey Bourne write that at first glance, a User Story looks simple, almost trivial. However, it contains the essence of the project deliverables. It describes the who, the what, and the why of every piece of delivered functionality. |
||
|
For Project Managers, Agile Is About Asking a Different Question[article] 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. |
||
|
Adapting to Change in Your Agile Strategies[article] Len Whitmore writes on using agile practices for the development of software. In the ten years since the Agile Manifesto, the agile development domain evolved, as evidenced by such things as the six levels of planning: strategy, release, iteration, daily, and continuous, with strategy appearing to be the least evolved of the planning levels. |
Len Whitmore
June 3, 2011 |
|
|
Applying Agile to Your Business Strategy[article] Matthew Gelbwaks writes that rather than applying a strategy to agile, you should apply the principles and values of agile to business or organizational strategy. Agile is the new way to compete and the new way to win at every level of the organization—from development to strategy. |
||
|
From Red Tape to No Tape: Organizational Misalignment with Agile Values[article] Charles Suscheck writes that if you’re in an organization that has signs of post-industrial orientation, now is a good time to take a fresh look at your organization’s underlying (and often oblique) belief system. |
||
 |
Experimenting: The Way Forward for Agile Development Teams[article] If you asked anyone on my team what agile practice is most responsible for our success over the past eight years, I bet they'd say retrospectives. But I wonder if it's not so much the retrospectives themselves, as the "small experiments" (to borrow Linda Rising's term) we perform to try to address our problem areas. |
|
|
Agile 2010 - Johanna Rothman - Agile Program Management[article]
Podcast
Agile 2010 - Johanna Rothman - Agile Program Management |
||
 |
From One Expert to Another: George Dinwiddie[interview] In this installment of our continuing conversations between software experts, Don Gray talks to George Dinwiddie about his work in the agile community—both before and after it got its name—and how agile approaches affect teams. |
|
|
ALM Tools in an Agile World[article] In this article, we not only help define agile, and how you and your team can get there; we also explain how ALM tools have agile's methodologies in mind and how they can help you reach your goal. Learn the the meanings behind the terms you need ot know, and why now is a great time to go agile. |
||
|
Displaying Build Numbers in Grails Apps[article] Being a fan of Continuous Delivery, identifiable builds, and Continuous Integration: I like to deploy web apps with a visible build number, or some other way of identifying the version. For example, having the build number on the login screen for example. |
||
|
Feature Injection: Part Two[article] The tag-line for Feature Injection is "As we pull value from a system, we inject features." So before we can start, we need to identify the business value. But how do we do that? This edition also expands on the 20/20 vision conference concept. |
||
|
How Do I Write Requirements Using Stories and Acceptance Criteria?—Part One[article] Russell Pannone writes that knowing what comes before the writing of stories, what comes after the writing of stories, and who is going to consume the stories sets the context for the form and substance of a story. |
||
|
From Red Tape to No Tape: Maximizing Agile in Your Organization[article] Companies using agile development must recognize that they won’t reap the benefits of agile without the correct organizational philosophy. Companies often don’t even realize that they are following a path that can limit agile adoption. Here, Charles Suscheck describes two organizational philosophies—one that is adverse to successful agile adoption and one that facilitates the agile processes. |
||
 |
Make Your Tele-Team Work[magazine] Can software development teams that include one or more telecommuters work as effectively as collocated teams? Learn how to overcome common obstacles faced by "tele-teams," illustrated with real-life examples. |
Pages
AgileConnection is a TechWell community.
Through conferences, training, consulting, and online resources, TechWell helps you develop and deliver great software every day.