We have 6069 guests and 6 members online

Agile Sponsors

HP


CollabNet


TechWell

Home > Articles > Columns > Articles

Articles

Original articles from industry thought leaders, analysts and software providers on a wide variety of topics related to agile development best practices and business adoption of agile ideas.


Defining Requirement Types: Traditional vs. Use Cases vs. User Stories

E-mail
Written by Charles Suscheck   
Wednesday, 18 January 2012 00:00

jun-09-bestbigI’ve worked with a lot of teams transitioning to agile. In each situation, user stories always seem to be a sticking point, with a common question being, “What are the differences between traditional requirements, use cases, and user stories?” I’d like to answer this question with a description and example of each requirement type. I’ll also use a running example: Imagine that we’re writing software for placement firms, and one of the firms has requested the ability to search for candidates for a specific role by specialty within a geographic location. For example, “I want to find all business analysts who are Sarbanes Oxley (SOX) experts within fifty miles of New York City.”

Last Updated on Wednesday, 18 January 2012 17:30
 

An Agile Software Shop

E-mail
Written by Rafael Alvarez   
Monday, 09 January 2012 15:37

Worksho[One of the most challenging situations involving adopting agile is when doing so in a software shop that has several specialized groups already in place forming silos: development, quality assurance (QA), business analysts (BA), software configuration management (SCM), documentation, architecture, database admin (DBA), and user experience (UX). These shops may or may not have fixed (non-negotiable) delivery dates with a very tight schedule, developing either commercial products or turnkey solutions for customers. The goal is to take these silos and form a cohesive team while delivering useful software by the required date.

Last Updated on Wednesday, 11 January 2012 10:24
 

The Zero Defect Vision, Part 1

E-mail
Written by Bob Schatz   
Monday, 09 January 2012 15:10

How many times have you had the conversation at work about how software is so complex and it should be an accepted fact that there are going to be a significant number of defects?

Would you be comfortable if your doctor, surgeon, airline pilot, bridge-builder, car manufacturer, or pharmaceutical company had similiar conversations?

Last Updated on Tuesday, 10 January 2012 12:59
 

The Zero Defect Vision, Part 2

E-mail
Written by Bob Schatz   
Monday, 09 January 2012 15:10

In " The Zero Defect Vision" Part 1, I explored how to develop strategies to eliminate errors and prevent defects in your product or service. In part two of my series, I will examine the common sources of errors in product development activities; by being aware of the things we can change in our environments, we can reach our goal of preventing errors. Then, a number of techniques can be employed in order to help teams work towards a zero defect goal.

People
In order to be able to recognize, and prevent, human error, it is important to understand that developing technology is a people business. Completely eliminating human error is not possible, so we should focus on minimizing the conditions that increase the possibility of error. Some of the factors to pay close attention to are:

Last Updated on Tuesday, 10 January 2012 12:58
 

How to Give an Accurate Answer

E-mail
Written by Scott G. Ames   
Tuesday, 13 December 2011 15:15

Answer“How long’s it gonna take?” My response: “Six weeks, plus or minus two days. No more.” In this article, I’ll give a rebuttal to Daryl Kulak’s article, “Let’s Stop the Wishful Thinking.” I will show why his beliefs about software estimating, while understandable, are questionable because of the advent of the Test Requirements Agile Metric (TRAM).

Last Updated on Tuesday, 13 December 2011 21:41
 

Edit Those Epics

E-mail
Written by Johanna Rothman   
Monday, 12 December 2011 00:00

Edit

I've been working with folks making their transition to agile. One of the hardest transitions is for the managers and technical leaders.

Managers are accustomed to working in timeboxes. To them, the iteration is a timebox. But, they also are accustomed to features spanning multiple timeboxes, and that’s not OK in agile.

Last Updated on Tuesday, 13 December 2011 11:28
 

The Two Metrics that Matter

E-mail
Written by Neil Fox   
Tuesday, 06 December 2011 17:14

1The global recession has strongly impacted the software development industry, including companies that develop software to support their traditional services. Anyone speaking to a development executive can feel these effects. The outcry is universal: “How can I do more with the same resources?” The need to be innovative, competitive, and cost effective has never been stronger than it is today. If necessity is the mother of invention, then current world economy is the mother of necessity.   Nearly every CIO or VP of R&D that I speak with is struggling to improve their time to market while increase the number of features delivered within stagnant or shrinking budgets. Two common objectives of software development teams address this need:

Last Updated on Wednesday, 07 December 2011 11:13
 

Six Steps for Implementing Agile Across the Organization

E-mail
Written by Ove Holmberg   
Friday, 04 November 2011 16:16

FeetOnce, I was hired at a big company as a team lead with a mission to create an agile team from a group of twelve skilled people. It was hard to transform the group (80 percent of whom were consultants) into a self-organized agile team consisting of 80 percent company employees, some of them offshored. This setup was a major success for me and my agile mentors as we transformed from a bunch of developers to an agile team, but I wasn’t able to celebrate because I had a problem. I was pushing too much self-organization onto the team, and one year of low (but increasing) velocity combined with stepping too hard and often on my boss’s toes, was fatal for me. My boss had to repeatedly explain to the CIO why we did not show the expected results.

Last Updated on Wednesday, 09 November 2011 11:39
 

Orders of Magnitude in Test Automation

E-mail
Written by Mike Kelly   
Friday, 04 November 2011 15:56

Grand CanyonMany teams focus on automation at the level that’s easiest to automate given the team makeup and the readily available tools. For some teams, that means lots of automated unit tests. For others, it can mean large suites of GUI-level automation tests. Developers tend to favor automation similar to their regular daily work, and testers tend to favor tools more closely resembling their normal test routines. Or, said another way, when the team looks to implement automation, they identify the closest hammer and start swinging.

Last Updated on Wednesday, 09 November 2011 14:39
 
<< Start < Prev 1 2 3 4 5 6 7 8 9 10 Next > End >>

Page 1 of 40
Cialis

Agile Marketplace - Announcements and Special Offers

Upcoming Webcasts
Sponsored by Urbancode - On Demand
Mastering Complex Application Deployment
Sponsored by CollabNet - Wednesday, August 24, 2011
Closing the Agile Loop: Continuous Integration, Continuous Information

ScrumWorks Pro – The World’s Best Agile Project Management Tool
Simply put, CollabNet’s ScrumWorks Pro is the best Agile project management solution on the market, bar none. More than 150,000 Agile professionals rely on the power and simplicity of ScrumWorks every day.  But don’t take our word for it – try it yourself for free. CollabNet is now providing the first 10 users of ScrumWorks Pro at no charge!
Download ScrumWorks Pro today!

The Business Case for ALM Transformation
Are legacy systems holding your company back?  Breakthrough these technical constraints with an open and scalable environment that meets your unique business need to transform. There is no reason to be locked into an obsolete platform. The output of a number of recent transitions from legacy systems, this is practical white paper shares lessons learned and illustrates how guidance and enablement can pave the way for change.
Download this Whitepaper