agile methods

[interview]

Agile Resiliency: An Interview with Jeff Dalton

Summary:

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.

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.

About the author

[article]

Excite and Delight Your Customers by Using the Kano Model

Summary:

Chandra Munagavalasa writes that because the requirements change over time, the product backlog is never complete. As the project progresses and more detailed information becomes available, the product backlog items and their rankings change continually. One of the many techniques available for ranking the product backlog is the Kano model.

Chandra Munagavalasa writes that because the requirements change over time, the product backlog is never complete. As the project progresses and more detailed information becomes available, the product backlog items and their rankings change continually. One of the many techniques available for ranking the product backlog is the Kano model.

About the author

[article]

The Three Amigos Strategy of Developing User Stories

Summary:

Developing software correctly is a detail-oriented business. George Dinwiddie writes on how using the Three Amigos strategy can help you develop great user stories. Remember, the goal is to have the work done just in time for planning and development. It should be complete enough to avoid stoppages to build more understanding, but not so far in advance that the details get stale.

Developing software correctly is a detail-oriented business. George Dinwiddie writes on how using the Three Amigos strategy can help you develop great user stories. Remember, the goal is to have the work done just in time for planning and development. It should be complete enough to avoid stoppages to build more understanding, but not so far in advance that the details get stale.

About the author

[interview]

How Agile Impacts Configuration Management and Testing: An Interview with Steve Berczuk

Summary:

Steve Berczuk is a regular contributor to TechWell and StickyMinds and a principal engineer and ScrumMaster at Fitbit in Boston. In this interview, Steve discusses configuration management and agile, helpful tools, and how testing has evolved over the years with the rise of agile.

Steve Berczuk is a regular contributor to TechWell and StickyMinds and a principal engineer and ScrumMaster at Fitbit in Boston. In this interview, Steve discusses configuration management and agile, helpful tools, and how testing has evolved over the years with the rise of agile.

About the author

[article]

How Depersonalizing Work and Managing Flow Can Humanize the Workplace

Summary:

Using metrics such as cumulative flow to monitor throughput and quantitative thinking may not seem very humanistic, but by depersonalizing the work being done, we can focus our energies on solving actual problems instead of conducting a daily witch-hunt and shaming people into high performance.

Using metrics such as cumulative flow to monitor throughput and quantitative thinking may not seem very humanistic, but by depersonalizing the work being done, we can focus our energies on solving actual problems instead of conducting a daily witch-hunt and shaming people into high performance.

About the author

[article]

Writing in an Agile World

Summary:

Sarah Johnson explains the role of writing in an agile world and how to educate your team members. Remember, agile takes into account that each situation is unique, and you need to determine what makes the most sense for your particular Scrum team.

Sarah Johnson explains the role of writing in an agile world and how to educate your team members. Remember, agile takes into account that each situation is unique, and you need to determine what makes the most sense for your particular Scrum team.

About the author

[article]

Big Agile: Enterprise Savior or Oxymoron?

Summary:

Lawrence Putnam explains whether or not big agile is an enterprise savior or an oxymoron. What if agile only works when teams and projects stay relatively small? That’s the question most CIOs want answered before investing scarce time, energy, or resources chasing the big agile paradigm.

Lawrence Putnam explains whether or not big agile is an enterprise savior or an oxymoron. What if agile only works when teams and projects stay relatively small? That’s the question most CIOs want answered before investing scarce time, energy, or resources chasing the big agile paradigm.

About the author

[article]

Scaling Agile Development for Enterprise Software

Summary:

Enterprise development organizations are increasingly embracing agile as a concept, if not entirely in practice. That’s because adopting and scaling agile methodologies for large, complex enterprise software projects can seem daunting. Larry Ayres shares some tips for scaling agile development for enterprise software.

Enterprise development organizations are increasingly embracing agile as a concept, if not entirely in practice. That’s because adopting and scaling agile methodologies for large, complex enterprise software projects can seem daunting. Larry Ayres shares some tips for scaling agile development for enterprise software.

About the author

[article]

Communicating Effectively in Agile Development Projects

Summary:

In today’s fast-paced workplace, software developers and project managers are confronted with a painful paradox. They are faced with continual pressure to accelerate the development process, but this “need for speed” can result in communication failures—and the accompanying project and quality problems.

In today’s fast-paced workplace, software developers and project managers are confronted with a painful paradox. They are faced with continual pressure to accelerate the development process, but this “need for speed” can result in communication failures—and the accompanying project and quality problems.

About the author

[article]

The Self-Abuse of Sprint Commitment

Summary:

Adam Yuret explains what can go wrong when teams blindly commit themselves to sprints; collaboration and quality suffer when we pressure people to work themselves to death by forcing them to promise things they cannot yet understand. Investing in systems-thinking approaches to improve the lives of our workers will pay dividends in improved quality, engagement, and creativity.

Adam Yuret explains what can go wrong when teams blindly commit themselves to sprints; collaboration and quality suffer when we pressure people to work themselves to death by forcing them to promise things they cannot yet understand. Investing in systems-thinking approaches to improve the lives of our workers will pay dividends in improved quality, engagement, and creativity.

About the author

Pages

AgileConnection is a TechWell community.

Through conferences, training, consulting, and online resources, TechWell helps you develop and deliver great software every day.