|
|
|
<<< Previous speaker
|
next speaker >>>
|
Scott Ambler, Founder of the Agile Modeling methodology
Scott W. Ambler is Chief Methodologist/Agile with IBM Software Group and he works with IBM customers around the world to improve their software processes. He is the founder of the Agile Modeling (AM), Agile Data (AD), Agile Unified Process (AUP), and Enterprise Unified Process (EUP) methodologies. Scott is the (co-)author of 19 books, including Refactoring Databases, Agile Modeling, Agile Database Techniques, The Object Primer 3rd Edition, and The Enterprise Unified Process. Scott is a senior contributing editor with Information Week.
Personal home page
Agile at Scale blog
|
Presentation: "Agile Modeling and Documentation "Best" Practices"
Time:
Tuesday 10:15 - 11:15
Location:
Store Sal
Abstract: How do you successfully model the complexities of modern-day software without getting bogged-down in mountains of paper work? How do you effectively engineer the requirements for your system? What techniques can you apply to analyze those requirements to architect and design your software? This presentation overviews the best practices of Agile Model Driven Development (AMDD), showing how modeling and documentation are important parts of any software delivery project, even agile ones.
Level: Intermediate
Keywords: Agile, Modeling, Documentation, Process
Workshop: "Modeling, Documentation, and Agile: Reality over Rhetoric"
Time:
Thursday 13:00 - 16:00
Location:
Trifork
Abstract:
Surveys have found that agilists are just as likely as traditionalists to model and to write documentation on their projects. But agile and traditional are as different as night and day, so what are agilists actually doing? In this workshop we will explore how agile teams are actually modeling and documenting in practice. After laying a bit of ground work we will self-organize into teams where we people with agile experience will describe how they actually approach modeling on agile projects. They will also describe how they approached deliverable documentation, and yes, even specifications (egads!). People without agile experience are still welcome as they will be asked to question everything that they hear from the people with agile experience. The goal of this workshop is to share strategies that work with, and very likely some strategies that don't work so well, to discuss the context and tradeoffs thereof, and finally to produce an "experiences report" which will be shared with the wider community.
|
 |
| |
