Se ha denunciado esta presentación.
Se está descargando tu SlideShare. ×

Rex - How User Stories can help you manage standard components of an IT project

Anuncio
Anuncio
Anuncio
Anuncio
Anuncio
Anuncio
Anuncio
Anuncio
Anuncio
Anuncio
Anuncio
Anuncio

Eche un vistazo a continuación

1 de 10 Anuncio

Rex - How User Stories can help you manage standard components of an IT project

Descargar para leer sin conexión

What is the link between your User Story catalogue and Data Model, Data Dictionary, Entity life cycle, all your tests (dynamic, static, ...).
Warning: subject a little bit technical ;-)

What is the link between your User Story catalogue and Data Model, Data Dictionary, Entity life cycle, all your tests (dynamic, static, ...).
Warning: subject a little bit technical ;-)

Anuncio
Anuncio

Más Contenido Relacionado

Presentaciones para usted (20)

Similares a Rex - How User Stories can help you manage standard components of an IT project (20)

Anuncio

Más de Jean-François Nguyen (20)

Más reciente (20)

Anuncio

Rex - How User Stories can help you manage standard components of an IT project

  1. 1. Methodology REX Return on EXperience How Agile practices can enhance standard components/deliveries of an IT project? How your User Stories backlog can help you manage standard components of an IT project such as: • Specification • Data model • Data dictionary • Organization model • Entity life cycle • Use Case catalogue • All your tests • … Warning: what follows is a little bit technical so if you are not familiar with those terms, maybe pass your way.
  2. 2. Methodology REX • How your customer/user test your application? • How do you build & make a demo of your application? • How do you make coexist Agile principles & Traditional IT project deliveries? Data model: • How your customer/user test your Data Model? ... with a Use Case • How do you build your Data model? ... with your Use Case catalogue Organisational model (roles & jurisdiction): • How your customer/user test your Organisation Model? ... with a Use Case • How do you build your Organisation model? ... with your Use Case catalogue Entity life cycle: • How your customer/user test your entity life cycle? ... with a Use Case • How do you build your entity life cycle? ... with your Use Case catalogue Example of concrete problems & questions about test faced by teams: • My User Story is heavy (10 pages long) with many tables describing static test on date format for instance • How do we manage our Unique Specification document and our User Story in JIRA? How do you manage all your Tests: • Static versus Dynamic? e.g. date format versus “As a BO operator I can …” (behaviour) • Small versus Large? e.g. price a vanilla versus price a strategy • Component versus Integrated? e.g. booking component versus integration with external referential • Technical versus Functional? e.g. Model View Control pattern versus “As a BO operator, I can ….”
  3. 3. Methodology How do you build & test your Data model? With your Use Case catalogue • Warning: for a large scope, build iteratively your Data Model i.e. define & follow your scope In/Out and increment workshop by workshop • In session, instantiate classes to test your User Story to make the group see how it will really run
  4. 4. Methodology How do you build & test your organization model? With your User Case catalogue From your Data model & sequence diagram deduce • For each role, what it can do & what it cannot do • A RA(CI) or read/wright matrix
  5. 5. Methodology How do your build & test your entity life cycle? With your Use Case catalogue From your entity life cycle, deduce: • The list of status • The action/event to pass from one status to another one
  6. 6. Methodology Functional test add Value for the customer, Static test is not. So, don’t overload User Story with static test! Split your Tests by category e.g. • Static versus Dynamic e.g. date format versus “As a BO operator, I can ….” (behaviour) • Small versus Large e.g. price a vanilla versus price a strategy • Component versus Integrated e.g. commission component versus integration with external Referential • Technical versus Functional e.g. Model View Control pattern versus “As a BO operator, I can ….
  7. 7. Methodology Tips for an efficient workshop • Meeting efficiency = Team Rules • Efficient meeting = “Work + Shop”
  8. 8. Methodology Tips to avoid frictions within the Team To avoid friction within the team, make it define what means ‘Ready’ & ‘Done’
  9. 9. Methodology Work Breakdown Structure (WBS) evolves with the team maturity on the subject Work Breakdown is not a goal but a mean: so don’t spend to much discussion on it
  10. 10. Methodology Work Breakdown Structure (WBS): reminder of what is an Epic, a Feature and a User Story Epic, Feature & User Story are the base of the Agile Work Breakdown Structure

×