agile

Articles

Performing a Simple Process Health Checkup

Does your software development process need tuning? How can you tell if it isn't running as well as it could be? In this week's column, Jeff Patton offers a diagnosis checklist for your team to help assess the vital statistics of your current development process.

Jeff Patton's picture Jeff Patton
Rocks into Gold: Part 2

This short book, written by Clarke Ching, is a "biztech" parable for software developers who want to survive—and then thrive—through a credit crunch. We have republished the book in a four-part series. In part two, Bob, Bill, and Sam discover how a rocky economy can flip project costs and return on investments and how much money could be lost by canning the FBU project. Can they use these projections to save the project and their jobs?

Clarke Ching's picture Clarke Ching
The Cost of Coexistence

Some organizations want to make the transition to agile, but aren't ready to trade in their old ways overnight. They'd rather spend some time getting to know agile—letting it coexist alongside already established, traditional methodologies. In this article, Michele Sliger and George Schlitz explain that such coexistence is possible, but that there is a cost of coexistence of which all organizations should be aware.

Dissecting the Product Owner role

Like Coach and Scrum Master the Product Owner is a new term for a new role. While Coach and Scrum Master are completely new roles added by Agile methods the Product Owner is an extension of an existing role. Or rather, it is an extension to two existing roles.

The role of Product Owner was introduced by Scrum. Teams following XP prefer to talk about a Customer. What ever the role is called it is concerned with: deciding what should be in the next iteration, prioritising work, providing guidance on what is being built and ensuring value is created.

Allan Kelly's picture Allan Kelly
An Agile Approach To Retail: A Data Intrinsic Development Case Study

Agile software development challenges traditional software development approaches. Rapidly changing environments characterized by evolving requirements and tight schedules require software developers to take an agile approach. These methods include practices such as short iterations, frequent releases, simple and emerging design, peer review, and on-site customer participation.

 

Dinesh  Mohata's picture Dinesh Mohata
How Agile Practices Reduce Requirements Risks

Requirements risks are among the most insidious risks threatening software projects. Whether it is having unclear requirements, lack of customer involvement in requirements development, or defective requirements, these troubles are a major culprit in projects that go awry. As requirements expert and agile coach Ellen Gottesdiener explains, agile practice can go a long way in mitigating those risks.

Ellen ellensqe's picture Ellen ellensqe
Postmodernism in Software Development

Recent history has ushered in the postmodern era in all its fragmented glory. With its arrival comes the displacement of the absolute, the certain, and all that characterizes the modern age. Along with changes in art, politics, and philosophy— there are reverberations in business and technology. The societal shift from Modernism to Postmodernism mirrors and reinforces a shift in software development from traditional waterfall to non-linear Agile methods.

Ryan  Fogarty's picture Ryan Fogarty
Timing Matters in Managing Change

Implementing change can be a colossal challenge. People tend to prefer what's familiar, safe, and predictable to that which is new, unfamiliar, uncertain, confusing, or potentially risky. But the timing of a change effort can influence how readily people accept the change and adjust to it.

Naomi Karten's picture Naomi Karten
Rocks into Gold: Part 1

This short book, written by Clarke Ching, is a "biztech" parable for software developers who want to survive—and then thrive—through the credit crunch. We have republished the book in a four-part series. In part one, we meet the main characters who have just found out that their jobs are on the line after discovering their major client's business is failing. Follow the story as our characters fight to keep their jobs by implementing creative business ideas and management skills taken from agile development.

Clarke Ching's picture Clarke Ching
ScrumBut: Failure to Deliver

In this article, Michele Sliger discusses one of the more common "ScrumBut" practices that, while allowing teams to say "We suck less," isn't really in keeping with intended Scrum practices. This ScrumBut practice is the persistent failure of the team to complete the agreed-upon features in the iteration or sprint.

Michele Sliger's picture Michele Sliger

Pages

AgileConnection is one of the growing communities of the TechWell network.

Featuring fresh, insightful stories, TechWell.com is the place to go for what is happening in software development and delivery.  Join the conversation now!