Part IITechnical Track: Design & ProgrammingThis webinar focuses on what developers must attend to when building systems with Agile methods. It discusses an alternative to the choices of:
| « | July 22, 2008 - August 21, 2008 | » |
|---|---|---|
07 / 22
| ||
07 / 23
| ||
07 / 24
| ||
07 / 25
| ||
07 / 26
| ||
07 / 27
| ||
07 / 28
| ||
07 / 29
| ||
07 / 30
| ||
07 / 31
| ||
08 / 1
| ||
08 / 2
| ||
08 / 3
| ||
08 / 4
| ||
08 / 5
| ||
08 / 6
| ||
08 / 7
| ||
08 / 8
| ||
08 / 9
| ||
08 / 10
| ||
08 / 11
| ||
08 / 12
| ||
08 / 13
| ||
08 / 14
| ||
08 / 15
| ||
08 / 16
| ||
08 / 17
| ||
08 / 18
Start: 2:00 am
Start: 12:00 pm
Part IIManagement Track: ProcessThis webinar discusses how Scrum#'s enterprise and product focus improves on the standard method of managing with Epics and User Stories. By stepping back to include product portfolio management, Scrum# facilitates working on the right product features across the enterprise, not just working on the right stories in a project. Topics discussed include: | ||
08 / 19
| ||
08 / 20
| ||
08 / 21
Start: 6:00 am
There runs a heated debate about how to build application architectures. Many practitioners believe you must design up front, others feel that doing so leads to over-design. Unfortunately, much of this debate is based on practices, not principles. Practices must change when one finds oneself in a different context. Principles do not. This talk presents a background of several useful principles which can help in building an application architecture dynamically. Start: 6:30 am
The advent of agile methodologies have caused concern and confusion in many an SQA organization; are agile practices like Test Driven Development and Acceptance Testing about to drive the SQA teams and practitioners into irrelevance? To the contrary, with a little adjustment SQA actually emerges in a leading role in software development process!This talk will show how lean/agile methodologies, by their nature, reassign SQA a leading role in software development through the practice of Acceptance Testing and Test Driven Development. We will: | ||
