hack your process

Hack Your ProcessExcommunicate yourself from the cargo cultPresented by Damian Brady (@damovisa) – Solution Architect @ SSW

Twitter Live Backchannel: #SSWDev

Delivering Awesome Web Applications

ASP.NET Web Forms

ASP.NET MVC

Software Architecture

Scrum

Team Foundation Server

Mobile Web Applications

Technology aficionado

TFS ASP.NET + MVC HTML5 + CSS + JS Web Forms Windows Forms

Damian Brady – SA @ SSWw: damianbrady.com.au | e: DamianBrady@ssw.com.au | t: @damovisa

Agenda

The point of process When to deviate from the path (and

when not to!) Important points Questions/discussion

The point of processWhy do we do what we do?

The point of process

Why do we have Scrum, or XP, or Kanban, or…?

Agile > Waterfall

But why adopt a different “formal” method?

Excommunication

Cargo Cult

Agile Manifesto

Inspect and adapt

Scrum, XP, Kanban are proven ways to meet the agile goals.

No limits

… but …

Don’t change until you understand

Consider that you might just be doing it wrong

Fix the existing process instead of changing it

When to deviateAnd when not to

When to deviate

What are you losing? Has it been replaced?

Three common examples:

Organisational restrictions beyond your control

Unpredictable work

Non-standard projects

Organisational restrictions

e.g. Upfront fixed-price fixed-schedule is a must

External vs Internal process

Dev Lead / Project Manager: Protect your team!

Tracking extra data

Unpredictable work

e.g. Support and Dev team are the same

You can’t track what you don’t record!

Non-standard projects

E.g. R&D Projects

You can often fit these into Scrum Timeboxed spiking

tasks Reduced availability

What are your goals?

Spiking is not just for software

Spike your process

Be prepared to change back

“Responding to change”

When NOT to deviate

Because it’s annoying

Don’t be hamstrung by your software Ditch the tool before ditching the process

Important pointsKey takeaways

Important points

Agile is about: Communication Reacting

It’s a team sport - honesty and trust

Measure

Change for the right reasons

Protip

Constant change == alarm bells

To sella changing processto management,put it in $ terms.

Anything

Summary

The point of process When to deviate from the path (and

when not to!) Important points Questions/discussion

Your Questions?

Other resources

How to implement Scrum using TFS 2012 – Gerard Beckerleg

Agile Anti-Patterns – Sander Hoogendoorn

SSW Scrum Consulting

Ping me maybe?

DamianBrady@ssw.com.

au

http://

damianbrady.com.au/

twitter.com/damovisa

Delivering Awesome Web Applications

Thank You!

Sydney | Melbourne | Brisbane | Adelaide

info@ssw.com.au

www.ssw.com.au