A few years ago, I worked at a company that had recently adopted Extreme Programming. After slogging through a few books about how XP worked, I refused to do the putting requirements on 3″ x 5″ cards, falling back to what I was comfortable with — wireframes. The wireframes were never really complete and detailed, but for six months, we ran an Agile development framework that ran on rails — so smooth, in fact, that we rarely pulled features.
That was a pretty small team. In larger teams, Thinking and Making talks about a change to their development process that successfully handled managing the requirements gathering process in an Agile environment. Read on…
- The Washing Machine vs. Waterfall Requirements Gathering
- Consultant Thursdays: Project Management Basics
- Seven Reasons Why Agile And Scrum Works For Web User Experience
- What’s Your Visual, Kenneth: The Value Of Wireframes
- Consultant Thursdays: Don’t Gather Requirements, Drive Them