Brazil Scrum Gathering 2009

Pessoal! Estarei na próxima semana apresentando um trabalho inédito no Brazil Scrum Gathering 2009, em São Paulo. Nele, vou apresentar, pela primeira vez, um modelo de "Project Story" que estou concebendo para definir de forma rápida e efetiva o escopo de um projeto de software. É uma idéia que tem dado certo de trabalhar com um template de Project Charter com estruturas semelhantes à User Story.

Espero vê-los por lá!!
--------------------------

RESUMO DO TRABALHO
From Vision Statement to Product Backlog:
An Effective Way to Quickly Develop Project and Product Requirements

Wednesday, 13 May 2009 from 11:15 to 12:30

Product Backlog (PB) is a high-level description about what have to be done in a project performed with Scrum. It is well known that PB has to be written (or specified) by the Product Owner (PO), who knows the business rules and what software requirements have to be developed. The problem in this case is that sometimes neither PO nor team members know how to structure a mind process to develop project and product requirements. A systemic view of the business context and the NLP S.C.O.R.E. Model can help a Scrum team to quickly develop a useful PB based on User Stories. In this talk, we will show how to combine these assumptions to develop in PO and team members new communication skills for better working with software requirements.

TOPIC:

Most Neuro-Linguistic Programming (NLP) is oriented around defining a present state and a desired state, and then identifying and applying a technique that will hopefully help someone get to their desired state. The S.C.O.R.E. Model enriches that description by adding a few more simple distinctions. The letters stand for Symptoms, Causes, Outcomes, Resources and Effects. These elements represent the minimum amount of information that needs to be addressed by any process of change. We will show how to think about software as a “resource” that provides desirable “effects” in a business environment, improving process “outcomes” by eliminating the “causes” of undesirable “symptoms”. The User Story framework showed to be powerful when developing a PB based on these assumptions.

OBJECTIVES:

1. How to use a systemic view (process thinking) to understand the project scope?
2. How to use the S.C.O.R.E. Model to write a simple and powerful business plan for the project?
3. How to challenge software requirements with the User Story framework?