Avoiding Coupling and Using Mocks In Agile Projects
Scrum# Webinar Series
Webinar Registered Access Lean-Agile
This content is available to Registered Users, Subscribers, or select Customers Only.
Most of the content in the resources section is available by merely registering at the site.
If you’ve taken one of our courses, please send a note to register@netobjectives.com and include the name and date of the course you took. If it was an on-site course, please include the name of the company as well.
Most of the content in the resources section is available by merely registering at the site.
If you’ve taken one of our courses, please send a note to register@netobjectives.com and include the name and date of the course you took. If it was an on-site course, please include the name of the company as well.
This webinar is part of the Scaling Scrum to the Enterprise with Lean Software Development series.
While full up-front designs are not the proper approach in virtually all agile projects, no design up front can also be a problem. This webinar discusses some techniques for decoupling modules early on. In other words, although we may not know how things will change, we often know of dependencies between modules that will morph over time. This webinar presents three case studies:
- Decoupling informational dependencies between components
- How to define the API for a component being built by one group and used by another
- Using mocks to never be blocked - avoiding delays caused by dependencies of different tiers
Publish Date
09/03/2008
Length
60 minutes
