Agile Modeling

2,898 views

Published on

Published in: Technology
1 Comment
3 Likes
Statistics
Notes
No Downloads
Views
Total views
2,898
On SlideShare
0
From Embeds
0
Number of Embeds
20
Actions
Shares
0
Downloads
86
Comments
1
Likes
3
Embeds 0
No embeds

No notes for slide

Agile Modeling

  1. 1. Otavio Ferreira (@otaviofff)Technical Architect, Scrum Master
  2. 2. • Agile Manifesto• Agile Modeling (AM)• Agile Model Driven Development (AMDD)• Agile Unified Process (AUP)
  3. 3. • Pluggable approach to project documentation• Adaptable documentation, according to the characteristics imposed by any given project – Project size / Level of detail • High abstraction level: Fewer artifacts • Low abstraction level: More artifacts – Development process paradigm • Iterative & Incremental • Waterfall
  4. 4. Project Documentation Envisioning Development Essential Envisioning Extended Envisioning Iterative Development[WF1] Initial Business [WF1] Extended [WF1] Iteration Planning +Definitions Requirements Envisioning Modeling[WF2] Initial Process [WF2] Initial Risk [WF2] Model StormingDefinitions Assessment[WF3] Initial Requirements [WF3] Initial Management [WF3] TDD + CI +Envisioning Definitions Refactoring[WF4] Initial Architectural [WF4] Iteration TrackingEnvisioning Process phase plug-in Process paradigm plug-in [WF5] Iteration Closing Process visibility plug-in Workflow plug-in
  5. 5. • Process Phases – Two phase organization – Agnostic towards any specific methodology – Agnostic towards any process paradigm – Process phase plug-ins • Envisioning • Development
  6. 6. • Process Phases  Envisioning – Kickoff stage – Team and other stakeholders focus on initial project planning – Process visibility plug-ins • Essential • Extended
  7. 7. • Process Phases  Envisioning  Essential – Drives the team in order to… • Make initial business decisions • Set up basic process variables • Select initial product requirements • Design high-level product architecture
  8. 8. • Process Phases  Envisioning  Essential
  9. 9. • Process Phases  Envisioning  Essential – Workflow plug-ins• WF1: Initial Business Definitions • WF3: Initial Requirements Envisioning – Business Background – Product Vision – Business Cases – Product Actors• WF2: Initial Process Definitions – Product Backlog – Definition of Done – Product Release Plan – Assignment of Roles – Product UI Flow Model – Agenda of Rituals – Product Glossary • WF4: Initial Architectural Envisioning – Domain Model – Analysis Model – Design Model – Deployment Model – Implementation Model – Change Cases
  10. 10. • Process Phases  Envisioning  Extended – Drives the team in order to… • Assess project risks • Analyze product requirements further • Define project management variables
  11. 11. • Process Phases  Envisioning  Extended
  12. 12. • Process Phases  Envisioning  Extended – Workflow plug-ins• WF1: Extended Requirements • WF3: Initial Management Definitions Envisioning – Project Control – Product Scope (In, Out) – Project Milestones – Project Assumptions – Project Acceptance and Signoff – Project Dependencies – Organizational – Project level – Stakeholders• WF2: Initial Risk Assessment – Risk Severity Matrix – Impact – Probability
  13. 13. • Process Phases  Development – Team sets out to construct the software – Process paradigm plug-ins • Iterative & Incremental • Waterfall
  14. 14. • Process Phases  Development  Iterative – Processes addressed by this instance • UP (Unified Process) • XP (Extreme Programming) • Scrum • Kanban
  15. 15. • Process Phases  Development  Iterative
  16. 16. • Process Phases  Development  Iterative – Workflow plug-ins• WF1: Iteration Planning & Modeling • WF4: Iteration Tracking – Sprint Backlog – Sprint Burndown Chart• WF2: Model Storming – Sprint Task Board – Design Model – Sprint Story Board – Change Cases • WF5: Iteration Closing• WF3: TDD + CI + Refactoring – Release Burndown Chart – Test Model (Executable) – Release Burnup Chart – Release Plan – Team Velocity Chart – Retrospective Report
  17. 17. • Process Phases  Development  Waterfall – Undefined
  18. 18. • Additional Documentation – Applied when needed, according to the project – Artifacts • User Documentation • Support Documentation • Operation Documentation

×