Has 'Agile' Killed 'Use Cases'?
Are Use Cases, the long-form way to document functional requirements, now dying or even dead? Has Agile killed them?
ALL
DOWNLOADS
ARTICLES
REFERENCE
PROCESS
ON-DEMAND WEBINARS
TRAINING LIVE WEBINARS USER-GENERATED |
|||
Books Events Links White Papers Wikis | |||
Language: | All English Arabic French Japanese Korean Portuguese Romanian Russian Spanish | ||
Access: | All Free Premium | ||
Newest Title | |||
All A B C D E F G H I J K L M N O P Q R S T U V W X Y Z |
Are Use Cases, the long-form way to document functional requirements, now dying or even dead? Has Agile killed them?
The push toward more Agile, open-source development has driven developers to cooperate more by using social media tools and collaborative environments.
The reality for many of our colleagues is that being agile is easier said than done.
One problem that sometimes arises as an agile contractor is when the prospective client wants an upfront commitment on the scope of the project, but the Scrum consultant feels there isn’t enough info to estimate a backlog for the RFP phase.
How long does it take an organization to reorganize in order to adopt Scrum? Three hours. Really.
Any organization adopting agile faces the challenge of figuring out how to measure success. Answering these questions without compromising the spirit of an agile transformation is critical to adoption.
Many teams struggle with defining "good" agile stories.
"To you I'm an atheist; to God, I'm the Loyal Opposition." - Woody Allen |