agile transition

Articles

Scrum standup meeting The Scrum Daily Standup Meeting: Your Questions Answered

The daily standup, or daily scrum, is a short meeting the team uses to briefly communicate work commitments with each other. Dick Carlson answers some questions that agile teams, management, stakeholders, and those who are thinking about transitioning to agile commonly have about these daily standup meetings.

Dick Carlson's picture Dick Carlson
Test automation Test Automation in the Agile World

After decades of talking about test automation, the agile movement suddenly seems to be taking it seriously. You might be wondering what all the buzz is about. Sanjay Zalavadia talks about why test tooling is suddenly so critical, when teams should think of automating, and how to bring the change so that your team will embrace it.

Sanjay Zalavadia's picture Sanjay Zalavadia
Chart organizing agile requirements Stories, Epics, and Tasks: Organizing Agile Requirements

Some teams only work with stories, but it can be difficult for a team new to agile to write stories that are easy to understand and provide value every time. An alternative is to add epics and tasks. Understanding the differences between each level and knowing what size story to use for each situation will improve the accuracy of your sprint planning.

Allan Kelly's picture Allan Kelly
Griffin Jones discusses Regulated Software Testing STAREAST 2015 Interview with Griffin Jones on Regulated Software Testing
Video

In this interview, STAREAST speaker Griffin Jones discusses his experience at the conference, as well as his presentation titled, "The Workshop on Regulated Software Testing." It's a peer workshop dedicated to improving the practice of testing regulated systems. 

Jennifer Bonine's picture Jennifer Bonine
Agile team cooperation How Business Teams Can Embrace Agile Techniques

As agile principles and practices receive greater organizational exposure, business teams are embracing certain aspects of agility that were traditionally reserved for technology teams. This article details the experiences of a group of people with business roles who have adopted some agile methods and how their teams have benefitted.

Eric  King's picture Eric King
Fish jumping into bigger bowl Welcome to Agile: A Developer’s Experience

In this article, a developer shares his personal experience with the transition from a waterfall environment to an agile one. He compares what it was like for him coding, learning, and communicating using each methodology, and he shares what it was like making the change to agile—and why he's never looking back.

Kris Hatcher's picture Kris Hatcher
Global customers Know Your Customers: They Can Help You Write Better User Stories

Too many user stories begin, "As a user …" Who is your user? Or, more accurately, who are they? Improving your understanding of the types of customers who use your software lets you see multiple products where previously, there was only one—and identifying dedicated products will help you prioritize and accelerate delivery.

Allan Kelly's picture Allan Kelly
Balanced scale Relieving Agile Tension: How to Write Small Stories That Still Have Value

There are two practical goals for user stories: Each story should be beneficial to the business, and each story should represent a small piece of work. However, there is tension between these rules, and they often push in opposite directions. This article discusses how to keep stories small and tasks manageable, while ensuring they retain business value.

Allan Kelly's picture Allan Kelly
Do You Give Your Manager What She Wants or What She Needs?

High-stress situations arise when you have to respond to management's never-ending tough questions regarding product delivery. According to Johanna Rothman, you can properly set expectations without stress simply by understanding your manager's point of view.

Johanna Rothman's picture Johanna Rothman
Stacked rocks: work not done The Art of Maximizing Work Not Done

One of the twelve principles behind the Agile Manifesto is “Simplicity—the art of maximizing the amount of work not done—is essential.” Why is this principle called an art, while the others aren’t? And why should we maximize the amount of work "not" done? This article analyzes the importance of simplicity in agile projects.

Ledalla Madhavi's picture Ledalla Madhavi

Pages

AgileConnection is a TechWell community.

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