Articles

Please enter an article title, author, or keyword
From One Expert to Another: Meeta Prakash

Meeta Prakash has been involved in testing for twelve years. In this installment of the From One Expert to Another interview series, Anne-Marie Charrette speaks with her about her testing experience, coaching, and the importance of understanding the different cultures with which you engage.

Anne-Marie  Charrette's picture Anne-Marie Charrette
Helping the Customer Stick to the Purpose of a User Story

Lisa Crispin writes that you need to understand the purpose of a user story or feature. Start with the "why." You can worry later about the "how." The customers get to decide on the business value to be delivered. They generally aren't qualified to dictate the technical implementation of that functionality. It's up to the technical team to decide the best way to deliver the desired feature through the software.

Lisa Crispin's picture Lisa Crispin
Project Pyramid Estimating the Unknown: Dates or Budgets, Part 1

Almost every manager I know wants to know when a project will be done. Some managers decree when a project will be done. Some managers think they can decree both the date and the feature set. There is one other tiny small subset, those managers who ask, “When can you finish this set of ranked features?”

Johanna Rothman's picture Johanna Rothman
Is It Beautiful?—Aesthetics in Software Testing

With all the faces it presents, surely software can be said to possess or lack beauty. But, what does it mean to have beautiful software, and how do we evaluate it? In this installment of his series on philosophy and testing, Rick Scott takes a closer look at software aesthetics.

Rick Scott's picture Rick Scott
How to Lose a Customer

Giving your clients the opportunity to voice their opinions after conducting business with you is a great way to express your interest in continuing to work with them. Just make sure you're earnest in hearing their thoughts and that you don't simply think this is accomplished with a survey alone.

Naomi Karten's picture Naomi Karten
Edit Those Epics

It can be tricky for managers and technical leaders to make the transition to agile. They’re likely accustomed to doing things a particular way. What’s more, they may try to squeeze their old ways into the new, agile approach. Here, Johanna Rothman describes why that isn’t a good idea, especially regarding stories that are too big.

Johanna Rothman's picture Johanna Rothman
Agile or Not: How to Get Things Done

Agile software development always felt intuitive to me. Developing software incrementally, in close collaboration with the customer is the obvious way to deal with the uncertainty inherent in both software requirements and implementation. The technical practices of automating necessary but time consuming tests, and deploying, early and often are the obvious ways to give an team the ability to evaluate the  functionality you have and to to decide if the software works as expected. And it's also important to decide if what you built still makes sense given the current environment.

Steve Berczuk's picture Steve Berczuk
drawing a flow chart Getting to "Done" in Agile Development

When the tasks in the "Done" column needed more attention, the team created a "Done Done" column. Later, they created a "Done Done Done" column. In this article, Brian Bozzuto discusses how you can stop adding columns and honestly get to "done" without having to kid yourself.

Brian  Bozzuto's picture Brian Bozzuto
More on Being Done

Continuing the conversation from last week, Andy Singleton followed up on my post on being done with this post. Which is good as this is one of those questions that sounds simple in theory, but in practice contains some subtlety.

Steve Berczuk's picture Steve Berczuk
What Does "Being Done" Really Mean in Software Development?

Agile New England (which used to be called the New England Agile Bazaar, and which was started by Ken Schwaber) , has this wonderful activity before the main event each month: they host Agile 101 sessions, where people who know something about agile lead a short (30 minutes) small (about 10 people) class on agile basics for those who want to learn more about some aspect of agile. 

Steve Berczuk's picture Steve Berczuk

Pages

Upcoming Events

Apr 27
Jun 08
Sep 21