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: 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/post.php on line 2872

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/post.php on line 2833

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: 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/classes.php on line 345

Warning: Cannot modify header information - headers already sent by (output started at /homepages/21/d192906962/htdocs/agileux/wp-settings.php:512) in /homepages/21/d192906962/htdocs/agileux/wp-includes/feed-rss2.php on line 8
Agile UX http://www.agile-ux.com Agile Coaching, SCRUM and User Experience, Agile & Lean Management
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/post.php on line 2872

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
Sat, 10 Feb 2018 21:28:32 +0000
http://wordpress.org/?v=2.7 en hourly 1
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
Personas Method and Agile
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/link-template.php on line 107

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/link-template.php on line 132
http://www.agile-ux.com/2018/02/10/personas-method-and-agile/
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/link-template.php on line 107

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/link-template.php on line 132
http://www.agile-ux.com/2018/02/10/personas-method-and-agile/#comments

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
Sat, 10 Feb 2018 21:27:13 +0000
jc-Qualitystreet http://www.agile-ux.com/?p=661 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
Here a short presentation I gave recently (in french) that will make happy Agile UX practitionners. Personas : Mode d'emploi from Jean Claude GROSJEAN More about coaching? Mon offre de coaching Agile Le travail de coach Agile ]]>

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/link-template.php on line 107

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/link-template.php on line 132
http://www.agile-ux.com/2018/02/10/personas-method-and-agile/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
Hack your Culture - HACK YOUR MEETINGS
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/link-template.php on line 107

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/link-template.php on line 132
http://www.agile-ux.com/2013/07/30/hack-your-culture-hack-your-meetings/
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/link-template.php on line 107

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/link-template.php on line 132
http://www.agile-ux.com/2013/07/30/hack-your-culture-hack-your-meetings/#comments

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
Tue, 30 Jul 2013 12:51:05 +0000
jc-Qualitystreet http://www.agile-ux.com/?p=641 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

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
Changing the culture of an organization is a complex and multifaceted operation that requires a lot of effort: this is why I like the word  ”transformation” . This transformation can obviously be undertaken from various angles … hacking is one of them. (adsbygoogle = window.adsbygoogle || []).push({}); Hacking is a viral and [...]]]>

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/link-template.php on line 107

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/link-template.php on line 132
http://www.agile-ux.com/2013/07/30/hack-your-culture-hack-your-meetings/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
The Wheel of Agile Management
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/link-template.php on line 107

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/link-template.php on line 132
http://www.agile-ux.com/2013/03/18/the-wheel-of-agile-management/
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/link-template.php on line 107

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/link-template.php on line 132
http://www.agile-ux.com/2013/03/18/the-wheel-of-agile-management/#comments

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
Mon, 18 Mar 2013 17:32:55 +0000
jc-Qualitystreet http://www.agile-ux.com/?p=635 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
Inspired by classic coaching tools (like the wheel of life), this wheel of Agile Management helps me in my coaching activities with Managers involved in Agile transformation. The tool is visual and efficient, useful to explore current situation or to prepare coaching. Thank you to @bangalaurent helping me to formalize it! Obviously, the wheel is not fixed [...]]]>

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/link-template.php on line 107

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/link-template.php on line 132
http://www.agile-ux.com/2013/03/18/the-wheel-of-agile-management/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
AgileUX: Prototyping, Design Studio and Sketching
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/link-template.php on line 107

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/link-template.php on line 132
http://www.agile-ux.com/2012/05/26/agileux-prototyping-design-studio-and-sketching/
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/link-template.php on line 107

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/link-template.php on line 132
http://www.agile-ux.com/2012/05/26/agileux-prototyping-design-studio-and-sketching/#comments

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
Sat, 26 May 2012 00:02:30 +0000
jc-Qualitystreet http://www.agile-ux.com/?p=627 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
Here are the slides of the presentation I gave at Agile France 2012 (Paris) AgileUX - Prototyping, Design Studio and Sketching View more PowerPoint from Jc Grosjean ]]>

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/link-template.php on line 107

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/link-template.php on line 132
http://www.agile-ux.com/2012/05/26/agileux-prototyping-design-studio-and-sketching/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!
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/link-template.php on line 107

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/link-template.php on line 132
http://www.agile-ux.com/2012/03/01/user-story-checklist-be-ready-be-effective/
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/link-template.php on line 107

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/link-template.php on line 132
http://www.agile-ux.com/2012/03/01/user-story-checklist-be-ready-be-effective/#comments

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
Thu, 01 Mar 2012 00:02:58 +0000
jc-Qualitystreet http://www.agile-ux.com/?p=615 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
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 [...]]]>

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/link-template.php on line 107

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/link-template.php on line 132
http://www.agile-ux.com/2012/03/01/user-story-checklist-be-ready-be-effective/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
Visual Management… at Home!
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/link-template.php on line 107

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/link-template.php on line 132
http://www.agile-ux.com/2011/12/01/visual-management-at-home/
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/link-template.php on line 107

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/link-template.php on line 132
http://www.agile-ux.com/2011/12/01/visual-management-at-home/#comments

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
Thu, 01 Dec 2011 10:11:27 +0000
jc-Qualitystreet http://www.agile-ux.com/?p=612 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
Including the notorious “To learn list” in a mini format… At home, I don’t really need  a feedback door…, but the “Taskboard door”  is more useful Release 1 contains: An area dedicated to generic tasks (To do / In progresss; no need to track the done) An area dedicaded to learning tasks (crucial to me): need to [...]]]>

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/link-template.php on line 107

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/link-template.php on line 132
http://www.agile-ux.com/2011/12/01/visual-management-at-home/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
Remember the future… not only to mitigate cognitive biases
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/link-template.php on line 107

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/link-template.php on line 132
http://www.agile-ux.com/2011/11/27/remember-the-future-not-only-to-mitigate-cognitive-biases/
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/link-template.php on line 107

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/link-template.php on line 132
http://www.agile-ux.com/2011/11/27/remember-the-future-not-only-to-mitigate-cognitive-biases/#comments

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
Sun, 27 Nov 2011 17:06:41 +0000
jc-Qualitystreet http://www.agile-ux.com/?p=607 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
“Remember the Future” is one of the 13 games offered and popularized by Luke Hohmann. I’ve already talked about the Product Vision Box and Speed ​​Boat which I use regularly … it is now time to introduce you with another game… Remember the future … not only to mitigate cognitive biase your customers and users are not good [...]]]>

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/link-template.php on line 107

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/link-template.php on line 132
http://www.agile-ux.com/2011/11/27/remember-the-future-not-only-to-mitigate-cognitive-biases/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
Agile Testing Days 2011: Days 2… a report
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/link-template.php on line 107

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/link-template.php on line 132
http://www.agile-ux.com/2011/11/26/agile-testing-days-2011-days-2-a-report/
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/link-template.php on line 107

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/link-template.php on line 132
http://www.agile-ux.com/2011/11/26/agile-testing-days-2011-days-2-a-report/#comments

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
Sat, 26 Nov 2011 16:40:52 +0000
jc-Qualitystreet http://www.agile-ux.com/?p=584 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

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

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

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
DAY 1 was just amazing… see my previous report: Agile Testing days: Day 1 What a fabulous day! … to me the second day of the conference was less intense.  Keynotes were great but I was a bit disappointed by some sessions I attended… Esther Derby People & Patterns (Keynote) According to Esther, a basic problem is that [...]]]>

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/link-template.php on line 107

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/link-template.php on line 132
http://www.agile-ux.com/2011/11/26/agile-testing-days-2011-days-2-a-report/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
Collaborative workshop and The letter to Santa Claus: Act4
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/link-template.php on line 107

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/link-template.php on line 132
http://www.agile-ux.com/2011/11/20/collaborative-workshop-and-the-letter-to-santa-claus-act4/
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/link-template.php on line 107

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/link-template.php on line 132
http://www.agile-ux.com/2011/11/20/collaborative-workshop-and-the-letter-to-santa-claus-act4/#comments

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
Sun, 20 Nov 2011 22:04:35 +0000
jc-Qualitystreet http://www.agile-ux.com/?p=563 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
Or gaming & agile mindset at Home Christmas is coming and for the fourth year we’ve prepared during a great collaborative workshop with kids, our letter to Santa Claus (or technically speaking, our prioritized Backlog for Santa Claus) … (adsbygoogle = window.adsbygoogle || []).push({}); Step 2: Backlog Initialization Images are cut One [...]]]>

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/link-template.php on line 107

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/link-template.php on line 132
http://www.agile-ux.com/2011/11/20/collaborative-workshop-and-the-letter-to-santa-claus-act4/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
Agile Testing Days 2011: DAY 1 - What a fabulous Day!
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/link-template.php on line 107

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/link-template.php on line 132
http://www.agile-ux.com/2011/11/19/agile-testing-days-2011-day-1-what-a-fabulous-day/
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/link-template.php on line 107

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/link-template.php on line 132
http://www.agile-ux.com/2011/11/19/agile-testing-days-2011-day-1-what-a-fabulous-day/#comments

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
Sat, 19 Nov 2011 09:16:06 +0000
jc-Qualitystreet http://www.agile-ux.com/?p=517 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

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 Agile Testing Days (Nov 14-17 2011) is the annual European conference for and by international professionals involved in the agile world. As the French Ambassador of the conference  taking place this year in Potsdam (near Berlin), I couldn’t miss it. So, second participation, high expectations and absolutely NO DECEPTION! This first day was I think my [...]]]>

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/link-template.php on line 107

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/link-template.php on line 132
http://www.agile-ux.com/2011/11/19/agile-testing-days-2011-day-1-what-a-fabulous-day/feed/