Video: http://vimeo.com/4527751

Where do I begin?

Unit Testing ?

Process Smells

Contiguous Integration

User Stories

Start Small or Big

Where and How do I start

Source Control

Kanban

Iterations

Iteration Planning

What problems will I run into

XP

Scrum

TDD

How do you convince people to do agile?

Rigor/Discipline

How do I switch mid stream

How does agile affect my design

Methodologies - describe/differentiation

We are all doing agile no matter what we think. Did anything on your waterfall/rad/agile project change before the end of the project?

Quality

YAGNI - You aren't going to need it

DRY - Don't repeat yourself

It's about communication

Change is the only constant

Vocabulary

Methodologies

                XP

                Scrum

                Lean

                Kanban

Terms

                YAGNI - you ain't gonna need it. Don't over engineer, design, featureize, etc.

                DRY - Don't repeat yourself

                SOLID - http://butunclebob.com/ArticleS.UncleBob.PrinciplesOfOod

                TDD - Test Driven DESIGN (emphasis on design)

                BDD - Behavior driven design

                Iterations - Time blocks

                Sprints - Time blocks

                Technical Debt

                Cyclomatic complexity - http://en.wikipedia.org/wiki/Cyclomatic_complexity

Techniques

                User Stories

                Continuous Integration

                Source Control

                Inversion of Control/Dependency Injection

How Do I

                Where do I begin

                Process Smells

                Start Big or Small

                What problems do I run info

Other

                Agile army of one

                Rigor/Discipline

Discuss agile/xp not in terms of agile/XP but as: risk, cost, debt, capital, priority

It's about giving customers informed choices.

As an individual you can build doing agile practices. But be careful of the cowboy coders because they can out code you.  You need metrics.

How do we establish metrics?

Features vs Time issue is always part of the equation.

Customers/Business owners have rights to make "irrational" decisions

Sometimes the highest level of quality is not that important INITIALLY. When it becomes a long term proposal/business it becomes more important to implement quality

Risk vs Reward.

Technical Debt earns interest.

Technical Debt vs Features Chart

Technical Debt is high vs Features in the initial stages of a project.

Talk to customers in terms they understand.

How do we work within a cost boxed project?

Quality is a factor of risk and project cost.

Who decides what technical debt is?

Business stories vs Technical Stories

Project priorities

Technical debt can slip in. Sometimes the quick fix incurred a cost later on.

IOC Containers

·         StrutureMap

·         Windsor

·         Spring

·         NinJect