Sessions tagged as Agile

.NET Static Code Analysis

Presenter: Craig Berntson
Time: 1:30 PM – 2:45 PM, Saturday, May 22, 2010
Location: Franz Hall, Room 018

Static code analysis is a way to test your code without actually running it. It can detect errors that often times don't show up until the application is running at your customer's site. It also shows where your code doesn't follow best practices. In this session, you will learn how to manually perform static code analysis with FxCop and StyleCop and how to add these tools into a Continuous Integration process so the code analysis is performed automatically.

Agile Analysis for Developers

Presenter: Rod Claar
Time: 10:45 AM – 12:00 PM, Saturday, May 22, 2010
Location: Franz Hall, Room 222
Tags: Agile, Analysis

This session is a module in RippleRock’s Certified Scrum Developer course “Effective Scrum Developer”. This module is based on this user story: As a Developer, I want to quickly and accurately break down requirements, so that the work of delivering business value can be planned effectively. Rod Claar, Agile Practice Leader for RippleRock, will start with an interactive overview on identifying and creating User Stories. Then the discussion will turn to identifying the personas in your domain and how to unfold the stories to get to the size that an Agile Developer can build quickly and accurately. Rod will then discuss the sizing of stories in an agile environment and how a team can collaboratively estimate the work for predictable results and success! Rod will also demonstrate the creation of User Stories in Visual Studio and Team Foundation Server 2010.

Agile Architecture for Developers

Presenter: Rod Claar
Time: 3:15 PM – 4:30 PM, Saturday, May 22, 2010
Location: Franz Hall, Room 222

This session is a module in RippleRock’s Certified Scrum Developer course “Effective Scrum Developer”. This module is based on this user story: As a Developer, I want to create software components that are maintainable and efficient, so that the product will have a long life and adapt to new requirements easily. The topic of application architecture gets a lot of discussion in our industry. There are many dedicated and skilled software professionals that believe that the complete architecture must be known before a team should start work on the implementation. Rod Claar, Agile Practice Leader for RippleRock will discuss how much design is required at the beginning of the project and how developers can contribute to the development of a design that will last and be easy to maintain.

Agile Retrospectives for Continuous Improvement

Presenter: Diana Larsen
Time: 1:30 PM – 2:45 PM, Saturday, May 22, 2010
Location: Franz Hall, Room 108

Building on PDCA (Plan, Do, Check, Act) and other continuous improvement tools and techniques, Diana will lead an interactive session on how to focus and lead retrospectives for daily, incremental and milestone progress toward improving software team processes, methods, teamwork and practices. The workshop will include a flexible framework for designing effective retrospective sessions, as well as group processes to help team members learn, think and make decisions together.

Behavior-Driven Development (BDD) with MSpec 4 Fun, Profit and Beer!!

Presenter: Eric Ridgeway
Time: 7:30 PM – 10:00 PM, Saturday, May 22, 2010
Location: Franz Hall, Room 106

Come hang out and do some BDD using MSpec. We'll talk about BDD. What is it? Where does it fit in your testing story? And how BDD helps deliver value and make you feel as awesome as free beer? Best of all we are gonna do BDD, so come prepared to type!

Code Monkey tour of the ALM Features in Visual Studio 2010

Presenter: Charles Sterling
Time: 1:30 PM – 2:45 PM, Saturday, May 22, 2010
Location: Franz Hall, Room 222

In typical code monkey style Chuck will tour the 5 ALM themes for Visual Studio 2010: *Eliminate 'no repro' *Ensure architectural compliance *Embrace Manual Testing *Be proactive about agile project management *Understand existing architecture Be forewarned Chuck doesn't have a trained monkey he brings to his sessions and as a result tends to improvise with random audience members.