poised for change

21
Poised for Change Making and Keeping IT Systems Ready Rebecca Parsons Chief Technology Officer ThoughtWorks

Upload: rebeccajp42

Post on 10-May-2015

378 views

Category:

Software


2 download

TRANSCRIPT

Page 1: Poised For Change

Poised for Change Making and Keeping IT Systems Ready

!

Rebecca Parsons Chief Technology Officer

ThoughtWorks !

Page 2: Poised For Change

Quick delivery and release

The virtuous cycle includes:

Testable hypothesis

and then repeat

Measurement

Business Agility

Page 3: Poised For Change

So... what does it really take?

Page 4: Poised For Change

Experiment often

Be prepared to change quickly

Visibility into progress and performance

Rely on evidence not guesses

Balance predictability and opportunities

Factors

Page 5: Poised For Change

And How Do We Do That?

Page 6: Poised For Change

Continuous Delivery

Focus on achieving pragmatic software quality

Evolutionary architecture

Properly organized IT

Techniques

Page 7: Poised For Change

Early and often technical testing

Consider the time, scope, quality tradeoff

Focus on evolvability of the software

Trends often more valuable than values

Measure quality continuously

Internal Software Quality

Page 8: Poised For Change

And Where Do I Start?

Page 9: Poised For Change

Re-factor first for understanding, then for ease of change or re-use

Identify the hot-spots

Establish test coverage outside to inside

So is the Strangler Pattern

Abstraction is your friend

Remediating Code Quality Issues

Page 10: Poised For Change

Using event capture and routing

Used to add functionality around the edges of an old applicationUsing asset capture with bi-directional migration

Not used often enough

Very useful for addressing old complex code bases

Strangler Pattern

Page 11: Poised For Change

Last responsible moment

Postel’s Law

Architect for testability

Principles of Evolutionary Architecture

Page 12: Poised For Change

Minimizes technical debt from complexity

Delay decisions as long as you can

Maximizes the information you have

Decide early what your drivers are, and prioritize decisions accordingly

Last Responsible Moment

Page 13: Poised For Change

Beware the Silver Bullet

Page 14: Poised For Change

Continuous integration

Automate (almost) everything

Standardize environments as much as possible

End goal - deployments are boring

Automated testing

Continuous Delivery

Page 15: Poised For Change

What About the Organization?

Page 16: Poised For Change

Dilemma Cost control requires stability

whereas Value generation requires

responsiveness

Page 17: Poised For Change

The Same organization can’t do

both well

Page 18: Poised For Change

Consider the impact of Conway’s Law

Consider your differentiators (internal and external)

Separate commodity computing

Right-sized out sourcing

Manage at the portfolio level

What To Do?

Page 19: Poised For Change

Goal Business Agility

Page 20: Poised For Change

Lowering risk of experimentation

Architecting for real adaptability

Keeping systems poised for change

Aligning the organization

Maximizing visibility and feedback

Achieved by

Page 21: Poised For Change

Thank you! http://rebeccaparsons.com

http://www.thoughtworks.com @rebeccaparsons