|
|
|
Test-Driven Introduction to ASP.NET MVC
|
|
|
Developer
|
|
March 21, 2009 08:30 AM - 10:00 AM
|
|
Jonathan McCracken, ThoughtWorks
|
|
This session is designed for people who have never used the MVC framework before, and will take a test-first approach to each of the stages. After a tutorial giving the basic mechanics of the framework, participants will be asked to drive the code, and get tests to pass. Time permitted there will be several small labs to complete very simple requirements, with the facilitator walking around and helping participants work through the problems.
|
|
|
Threat Modeling
|
|
|
Developer
|
|
March 21, 2009 10:15 AM - 11:45 AM
|
|
David Woods, Solid House
|
|
Defensive programming techniques and technologies only go so far. There comes a point when we need to review our application with the mindset of attacking it. Threat modeling is one approach that has been gaining popularity in recent years. With threat modeling we will examine a simple application for attack vectors from several different aspects and learn how to reduce the vulnerabilities of our applications.
|
|
|
Windows Workflow Foundation
|
|
|
Developer
|
|
March 21, 2009 12:30 PM - 02:00 PM
|
|
David Paquette, P2 Energy Solutions
|
|
Windows Workflow Foundation (WF) is a powerful workflow technology introduced in .NET 3.0/3.5. This session is designed for developers who are new to the WF technology and for developers who have investigated WF but are not sure how the technology fits into their enterprise architecture. Topics covered will include workflow hosting, persistence, tracking, and communicating with running workflows.
|
|
|
Agile in Action: Taking one story through a iterative lifecycle
|
|
|
Agile
|
|
March 21, 2009 02:15 PM - 03:45 PM
|
|
Ram Swaminathan, Shaw
|
The Shaw PLT(BA, QA, UX and Dev) would like to demonstrate how we would work through a agile story to achieve working software in a iteration. We are going to take a simple feature and go through the life cycle of the story and demonstrate how all of our practices interact to produce working software within a iteration.
Four Practice Leaders from Shaw Communications will show how a story moves through a its lifecycle and how in the process we are redefining some the traditional definition of our various roles :
Ram Swaminathan, Practice Leader for Software Development
Heather Donnelly, Practice Leader for Business Analysis
David Cranstone is Shaw’s Practice Leader for Quality Assurance
Chad Fournier is Shaw’s Practice Leader for User Experience.
|
|
|
Iteration Planning and Tracking
|
|
|
Agile
|
|
March 21, 2009 12:30 PM - 02:00 PM
|
|
Jonathan McCracken, ThoughtWorks
|
Software is iterative in development and most project work is run this way. Length and day-to-day structure of those iterations are the key determining factors that make them successful at delivering working software. The session explains these factors as well as important information radiators (card wall, burn-up charts, velocity) that help keep a project on track. There is a fun activity which gives participants an idea of how to conduct iterations.
|
|
|
Take Your Continuous Integration Practice to the Next Level with Build Pipelines
|
|
|
Agile
|
|
March 21, 2009 08:30 AM - 10:00 AM
|
|
Eric Liu and Felix Wong, ThoughtWorks
|
|
Continuous Integration (CI) is a fundamental practice of Agile project teams, often associated with the compilation and automated testing of an application. Two interesting topics usually emerge over time -- how to address long build times, and a desire to extend CI to cover deployment. In this session, we present the build pipeline concept, and how it can help with these issues. We will also demonstrate this concept with a sample application code base using Cruise.
|
|
|
Transparency is like Sharing, and it's Good to Share
|
|
|
Agile
|
|
March 21, 2009 10:15 AM - 11:45 AM
|
|
Chris Ronak
|
|
Transparency, as an Agile Best Practice, is easily overlooked by Software Organizations wanting to improve accuracy, quality and achieve reliable releases. This is dangerous as it is one of the key principles in reducing risk and maximizing software competitive value. The truth is, it's not really that hard to implement and enforce a high degree of transparency - it's more a question of willingness, state of mind and team-self-confidence that stand in the way. Unveil the mystery! Outside stakeholders frequently get frustrated with software teams and departments because of a lack of transparency - and often for very good reason. In this presentation, Chris Ronak explores numerous processes and best practices that help improve software teams by adopting day-to-day behaviours and strategic principles that improve transparency.
|
|
|