Avoiding Coupling and Using Mocks In Agile Projects

Error message

  • Strict warning: Declaration of role_expire_handler_field_rid::pre_render() should be compatible with views_handler_field::pre_render(&$values) in require_once() (line 83 of /home2/netobje2/public_html/sites/all/modules/role_expire-7.x-1.0-beta2/role_expire/role_expire.views.inc).
  • Strict warning: Only variables should be passed by reference in eval() (line 3 of /home2/netobje2/public_html/modules/php/php.module(80) : eval()'d code).

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 de-coupling 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:

  • De-coupling 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

All the Details

Past Webinar
Wednesday, September 3, 2008
1 hour