Événement

APRIL Meeting of Agile CT: CREATING AGILE REQUIREMENTS (PART 2)

NOTE: This PART2 in a multi-part series on gathering requirements. PART1 in March presented the fundamentals. The APRIL meeting (PART 2) is a deeper dive on Persona generation, user story mapping and backlog creation. You can jump in at any time, the exercises are group-level. Attend this meeting is you want to learn more about collecting, developing and executing on AGILE SOFTWARE REQUIREMENTS...
==========================

Without good requirements, you cannot do good Agile. You need to know how to collect, gather and define requirements. Attend this meeting to learn how to build a real Product Backlog !

Everyone wants to know how to define requirements at the start of an Agile project. Old-school requirements insist that we do analysis, get PERFECT requirements, then do design, then development, then test. Sound familiar??

The results are in: this is a very ineffective approach to creating GREAT software.

The mechanics of creating requirements in an Agile way is very visual, tactile and collaborative. How we do requirements is the very heart of Agile. To really understand software Agility, you must experience how we gather and define requirements.

WARNING: Agile Requirements Gathering might cause discomfort and/or pain in the neck for traditional Business Analysts and Project Managers. May cause shortness of breathe in some individuals.

Attend to find out how to start gathering requirements in an Agile way! This is a multi-part series and you can jummp in at any time and have fun participating.

NOTE: Registration is a commitment to attend.