Business needs change, the competitive landscape changes, so system requirements must also be able to change if we want to deliver software that satisfies our customers. That's agile development in a nutshell, right? But what if we're so focused on the rapid development of working software "trees" that we don't see the "forest" of business requirements? In this issue we debate whether agilists really get requirements -- and what to do about it if they don't.
Feature This: Transforming Borland’s Development Process with Scrum
Posted June 30, 2006 | |
About The Author
Matthew Gelbwaks is a Managing Partner at North Main LLC. With more than 25 years’ experience helping clients execute on their vision, addressing complex problems, and developing process to speed value stream, he has assisted many organizations and businesses in becoming more successful. Mr. Gelbwaks works with clients worldwide via onsite workshops and ongoing mentoring. Much of his work focuses on organizational design and flow during digital… Read More
Don’t have a login?
Make one! It’s free and gives you access to all Cutter research.