All content and news on InfoQ about Customers & Requirements
Latest featured content about Customers & Requirements

- Architecture
- Topics
- Customers & Requirements,
- Collaboration
Although nearly everyone acknowledges the importance of user experience, usability often ends up pushed to the back of the queue. How then can we know whether what we are delivering makes sense and will work for our users? This presentation shows an approach to usability, focusing on activities in which users engage offers the potential for delivering dramatic improvements with much less effort.
-
By Larry Constantine
on Jul 07, 2008,
News about Customers & Requirements
- Agile
- Topics
- Customers & Requirements,
- Agile in the Enterprise
The Agile software development community discusses it successes on a regular basis, but rarely do we publicly discuss our failures. Robin Dymond has taken the first step by documenting one of his.
-
By Mark Levison
on Jul 10, 2008,
- Agile
- Topics
- Customers & Requirements
User stories, a common format for capturing agile requirements, could be more focused on business value. A traditional format for stating a user story is: "As a <type of user> I want <some functionality> so that <some benefit>." A value-centric replacement would be: "In order to <achieve some value>, as a <type of user>, I want <some functionality>."
-
By Chris Sims
on Jun 19, 2008,
Articles about Customers & Requirements

- Agile
- Topics
- Customers & Requirements,
- Agile Techniques
One of the great things about working as a consultant is the ability to try out many different ideas and adapting your personal favorite process to include things that work. This article gives the details about user story estimation techniques that Jay Fields has found effective.
-
By Jay Fields
on Jun 30, 2008,

- Agile
- Topics
- Delivering Value,
- Customers & Requirements
The role of the Scrum Product Owner is powerful, but challenging to implement. Success can bring a new and healthy relationship between customers/product management and development, even competitive advantage, but it comes at a price: organizational change is often required. In this article Roman Pichler looks at what it takes to succeed as a Product Owner.
-
By Roman Pichler
on May 14, 2008,
Interviews about Customers & Requirements

- Agile
- Topics
- Customers & Requirements,
- Methodologies,
- Agile in the Enterprise
Called "the grandmother" of the agile methodologies, DSDM V1 was released in 1995. The methodology is owned and collaboratively developed by the members of the not-for profit DSDM Consortium, and until V4.2 was only available to members. But the recent V5 or "Atern" release is now publicly available. Director Hugh Ivory provided an overview at Agile2007.
-
By Hugh Ivory
on Dec 19, 2007,

- Architecture
- Topics
- Domain Specific Languages,
- Artifacts & Tools,
- Customers & Requirements
Business users doing programming? In this interview, Charles Simonyi presents a radical new way of building software that separates business knowledge from software engineering knowledge. The claim is to simplify the creation process for software as business experts directly contribute using their customary domain description which results in accelerated innovation.
-
By Charles Simonyi
on Dec 18, 2007,
Presentations about Customers & Requirements

- Architecture
- Topics
- Domain Specific Languages,
- Artifacts & Tools,
- Customers & Requirements
Business users doing programming? Charles Simonyi and Henk Kolk presents how Intentional Software offers a radical new software approach that separates business knowledge from software engineering knowledge, which means that business experts can be more innovative and responsive to the changes in the domain.
-
By Charles Simonyi and Henk Kolk
on May 15, 2008,

- Ruby
- Topics
- Domain Specific Languages,
- Specifications,
- Language,
- Business Process Management,
- Customers & Requirements
Jay Fields presents his concept of Business Natural Languages (BNL). BNLs are a type of Domain Specific Language, designed to be readable by any subject matter expert, which allows to create maintainable specifications and documentation. The example language is shown using Ruby.
-
By Jay Fields
on May 08, 2008,
Books about Customers & Requirements

- Architecture,
- Agile
- Topics
- Domain Specific Languages,
- Customers & Requirements,
- Methodologies
Domain Driven Design is a vision and approach for designing a domain model that reflects a deep understanding of the business domain. This book is a short, quickly-readable summary and introduction to the fundamentals of DDD; it does not introduce any new concepts; it attempts to concisely summarize the essence of what DDD is, drawing mostly Eric Evans' book, as well other sources since published such as Jimmy Nilsson's Applying Domain Driven Design, and various DDD discussion forums.
-
By InfoQ.com
on Dec 08, 2006,