Deprecated: Assigning the return value of new by reference is deprecated in /homepages/21/d192906962/htdocs/agileux/wp-settings.php on line 512

Deprecated: Assigning the return value of new by reference is deprecated in /homepages/21/d192906962/htdocs/agileux/wp-settings.php on line 527

Deprecated: Assigning the return value of new by reference is deprecated in /homepages/21/d192906962/htdocs/agileux/wp-settings.php on line 534

Deprecated: Assigning the return value of new by reference is deprecated in /homepages/21/d192906962/htdocs/agileux/wp-settings.php on line 570

Strict Standards: Declaration of Walker_Page::start_lvl() should be compatible with Walker::start_lvl(&$output) in /homepages/21/d192906962/htdocs/agileux/wp-includes/classes.php on line 1199

Strict Standards: Declaration of Walker_Page::end_lvl() should be compatible with Walker::end_lvl(&$output) in /homepages/21/d192906962/htdocs/agileux/wp-includes/classes.php on line 1199

Strict Standards: Declaration of Walker_Page::start_el() should be compatible with Walker::start_el(&$output) in /homepages/21/d192906962/htdocs/agileux/wp-includes/classes.php on line 1199

Strict Standards: Declaration of Walker_Page::end_el() should be compatible with Walker::end_el(&$output) in /homepages/21/d192906962/htdocs/agileux/wp-includes/classes.php on line 1199

Strict Standards: Declaration of Walker_PageDropdown::start_el() should be compatible with Walker::start_el(&$output) in /homepages/21/d192906962/htdocs/agileux/wp-includes/classes.php on line 1244

Strict Standards: Declaration of Walker_Category::start_lvl() should be compatible with Walker::start_lvl(&$output) in /homepages/21/d192906962/htdocs/agileux/wp-includes/classes.php on line 1391

Strict Standards: Declaration of Walker_Category::end_lvl() should be compatible with Walker::end_lvl(&$output) in /homepages/21/d192906962/htdocs/agileux/wp-includes/classes.php on line 1391

Strict Standards: Declaration of Walker_Category::start_el() should be compatible with Walker::start_el(&$output) in /homepages/21/d192906962/htdocs/agileux/wp-includes/classes.php on line 1391

Strict Standards: Declaration of Walker_Category::end_el() should be compatible with Walker::end_el(&$output) in /homepages/21/d192906962/htdocs/agileux/wp-includes/classes.php on line 1391

Strict Standards: Declaration of Walker_CategoryDropdown::start_el() should be compatible with Walker::start_el(&$output) in /homepages/21/d192906962/htdocs/agileux/wp-includes/classes.php on line 1442

Strict Standards: Redefining already defined constructor for class wpdb in /homepages/21/d192906962/htdocs/agileux/wp-includes/wp-db.php on line 306

Deprecated: Assigning the return value of new by reference is deprecated in /homepages/21/d192906962/htdocs/agileux/wp-includes/cache.php on line 103

Strict Standards: Redefining already defined constructor for class WP_Object_Cache in /homepages/21/d192906962/htdocs/agileux/wp-includes/cache.php on line 431

Deprecated: Assigning the return value of new by reference is deprecated in /homepages/21/d192906962/htdocs/agileux/wp-includes/query.php on line 61

Deprecated: Assigning the return value of new by reference is deprecated in /homepages/21/d192906962/htdocs/agileux/wp-includes/theme.php on line 1109

Strict Standards: Declaration of Walker_Comment::start_lvl() should be compatible with Walker::start_lvl(&$output) in /homepages/21/d192906962/htdocs/agileux/wp-includes/comment-template.php on line 1266

Strict Standards: Declaration of Walker_Comment::end_lvl() should be compatible with Walker::end_lvl(&$output) in /homepages/21/d192906962/htdocs/agileux/wp-includes/comment-template.php on line 1266

Strict Standards: Declaration of Walker_Comment::start_el() should be compatible with Walker::start_el(&$output) in /homepages/21/d192906962/htdocs/agileux/wp-includes/comment-template.php on line 1266

Strict Standards: Declaration of Walker_Comment::end_el() should be compatible with Walker::end_el(&$output) in /homepages/21/d192906962/htdocs/agileux/wp-includes/comment-template.php on line 1266

Strict Standards: Redefining already defined constructor for class WP_Dependencies in /homepages/21/d192906962/htdocs/agileux/wp-includes/class.wp-dependencies.php on line 31

Strict Standards: Redefining already defined constructor for class WP_Http in /homepages/21/d192906962/htdocs/agileux/wp-includes/http.php on line 61

Strict Standards: call_user_func_array() expects parameter 1 to be a valid callback, non-static method GoogleSitemapGeneratorLoader::Enable() should not be called statically in /homepages/21/d192906962/htdocs/agileux/wp-includes/plugin.php on line 339

Strict Standards: strtotime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/21/d192906962/htdocs/agileux/wp-includes/comment.php on line 1590
User Story Checklist… Be Ready, be EFFECTIVE! | Agile UX
Strict Standards: call_user_func_array() expects parameter 1 to be a valid callback, non-static method GA_Filter::spool_analytics() should not be called statically in /homepages/21/d192906962/htdocs/agileux/wp-includes/plugin.php on line 339


Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/21/d192906962/htdocs/agileux/wp-content/themes/bible-scholar/header.php on line 50
Monday, April 23, 2018

Subscribe to the RSS Feed


Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/21/d192906962/htdocs/agileux/wp-includes/functions.php on line 41

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/21/d192906962/htdocs/agileux/wp-includes/functions.php on line 50

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/21/d192906962/htdocs/agileux/wp-includes/functions.php on line 52

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/21/d192906962/htdocs/agileux/wp-includes/functions.php on line 54

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/21/d192906962/htdocs/agileux/wp-includes/functions.php on line 55

Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/21/d192906962/htdocs/agileux/wp-includes/functions.php on line 41

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/21/d192906962/htdocs/agileux/wp-includes/functions.php on line 50

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/21/d192906962/htdocs/agileux/wp-includes/functions.php on line 52

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/21/d192906962/htdocs/agileux/wp-includes/functions.php on line 54

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/21/d192906962/htdocs/agileux/wp-includes/functions.php on line 55

User Story Checklist… Be Ready, be EFFECTIVE!

Posted by jc-Qualitystreet on
Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/21/d192906962/htdocs/agileux/wp-includes/functions.php on line 41

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/21/d192906962/htdocs/agileux/wp-includes/functions.php on line 50

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/21/d192906962/htdocs/agileux/wp-includes/functions.php on line 52

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/21/d192906962/htdocs/agileux/wp-includes/functions.php on line 54

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/21/d192906962/htdocs/agileux/wp-includes/functions.php on line 55
2012/03/01


Strict Standards: call_user_func_array() expects parameter 1 to be a valid callback, non-static method GA_Filter::the_content() should not be called statically in /homepages/21/d192906962/htdocs/agileux/wp-includes/plugin.php on line 166

Strict Standards: Non-static method GA_Filter::ga_parse_article_link() should not be called statically in /homepages/21/d192906962/htdocs/agileux/wp-content/plugins/google-analytics-for-wordpress/googleanalytics.php on line 440

Strict Standards: Non-static method GA_Filter::ga_parse_article_link() should not be called statically in /homepages/21/d192906962/htdocs/agileux/wp-content/plugins/google-analytics-for-wordpress/googleanalytics.php on line 440

Strict Standards: Non-static method GA_Filter::ga_parse_link() should not be called statically in /homepages/21/d192906962/htdocs/agileux/wp-content/plugins/google-analytics-for-wordpress/googleanalytics.php on line 430

Strict Standards: Non-static method GA_Filter::ga_get_domain() should not be called statically in /homepages/21/d192906962/htdocs/agileux/wp-content/plugins/google-analytics-for-wordpress/googleanalytics.php on line 410

Deprecated: Function split() is deprecated in /homepages/21/d192906962/htdocs/agileux/wp-content/plugins/google-analytics-for-wordpress/googleanalytics.php on line 413

Strict Standards: Non-static method GA_Filter::ga_parse_article_link() should not be called statically in /homepages/21/d192906962/htdocs/agileux/wp-content/plugins/google-analytics-for-wordpress/googleanalytics.php on line 440

Strict Standards: Non-static method GA_Filter::ga_parse_link() should not be called statically in /homepages/21/d192906962/htdocs/agileux/wp-content/plugins/google-analytics-for-wordpress/googleanalytics.php on line 430

Strict Standards: Non-static method GA_Filter::ga_get_domain() should not be called statically in /homepages/21/d192906962/htdocs/agileux/wp-content/plugins/google-analytics-for-wordpress/googleanalytics.php on line 410

Deprecated: Function split() is deprecated in /homepages/21/d192906962/htdocs/agileux/wp-content/plugins/google-analytics-for-wordpress/googleanalytics.php on line 413

Strict Standards: Non-static method GA_Filter::ga_parse_article_link() should not be called statically in /homepages/21/d192906962/htdocs/agileux/wp-content/plugins/google-analytics-for-wordpress/googleanalytics.php on line 440

Strict Standards: Non-static method GA_Filter::ga_parse_link() should not be called statically in /homepages/21/d192906962/htdocs/agileux/wp-content/plugins/google-analytics-for-wordpress/googleanalytics.php on line 430

Strict Standards: Non-static method GA_Filter::ga_get_domain() should not be called statically in /homepages/21/d192906962/htdocs/agileux/wp-content/plugins/google-analytics-for-wordpress/googleanalytics.php on line 410

Deprecated: Function split() is deprecated in /homepages/21/d192906962/htdocs/agileux/wp-content/plugins/google-analytics-for-wordpress/googleanalytics.php on line 413

Strict Standards: Non-static method GA_Filter::ga_parse_article_link() should not be called statically in /homepages/21/d192906962/htdocs/agileux/wp-content/plugins/google-analytics-for-wordpress/googleanalytics.php on line 440

Strict Standards: Non-static method GA_Filter::ga_parse_link() should not be called statically in /homepages/21/d192906962/htdocs/agileux/wp-content/plugins/google-analytics-for-wordpress/googleanalytics.php on line 430

Strict Standards: Non-static method GA_Filter::ga_get_domain() should not be called statically in /homepages/21/d192906962/htdocs/agileux/wp-content/plugins/google-analytics-for-wordpress/googleanalytics.php on line 410

Deprecated: Function split() is deprecated in /homepages/21/d192906962/htdocs/agileux/wp-content/plugins/google-analytics-for-wordpress/googleanalytics.php on line 413

The art of the specification in a agile context is above all collaborative. It’s also a matter of behavior.

As you know I like user stories. The format is a good way to express a requirement and to initiate the conversation between a Product Owner (supported or not by UX specialist, Business Analyst…) and the Team.

But of course, this short description, usually in one or two lines, is not sufficient to enable a Team to develop the functionality described… (see agile PROTOTYPING)

A generic template that must be adjusted to your own conditions of readiness

A generic template that must be adjusted to your own conditions of readiness

In short, the idea behind this precious checklist (inspired by Lisa Crispin and Janet Gregory’s book) is to facilitate the job of the Product Owner.

With this checklist, the Product Owner identifies the key elements that must come (in his context) with a specific User story. For example, these important test cases must be envisioned or a link to UX stuff, wireframe of the screen, UI library or a prototype must be provided.

This is also the place where you can start describing required business rules (the business rules paragraph was crucial for financial and supply chain projects I was involved in and we linked it to an ATDD approach).

The Product Backlog Refinement (the” forgotten” 5th Scrum ceremonial for grooming activities :) ) or other dedicated collaborative workshops are good opportunities to work on the checklist and to make sure that a specific user story will be ready to be taken and developed during the next sprint.

Product Backlog Refinement Agenda

Product Backlog Refinement Agenda

Then, several days later, first day of the new sprint, the sprint planning part I (scope definition) will be used to confirm the various elements, especially the conditions of satisfaction, and the engagement of the Team to develop, by the end of the sprint, the user stories discussed.

Remember: feedback and collaboration!

Comments are closed.

home | top