Top Banner
The Ultimate ALM Environment (circa 2010) James Crisp, .NET lead for Oz ThoughtWorks
54

The Ultimate ALM Environment (circa 2010) James Crisp,.NET lead for Oz ThoughtWorks Australia.

Jan 20, 2016

Download

Documents

Lenard Garrett
Welcome message from author
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Transcript
Page 1: The Ultimate ALM Environment (circa 2010) James Crisp,.NET lead for Oz ThoughtWorks Australia.

The Ultimate ALM Environment(circa 2010)

James Crisp, .NET lead for OzThoughtWorks Australia

Page 2: The Ultimate ALM Environment (circa 2010) James Crisp,.NET lead for Oz ThoughtWorks Australia.

Source: Wikipedia (http://en.wikipedia.org/wiki/Application_lifecycle_management)

Page 3: The Ultimate ALM Environment (circa 2010) James Crisp,.NET lead for Oz ThoughtWorks Australia.

Effective

Productivity

Quality

Cost

Morale

Page 4: The Ultimate ALM Environment (circa 2010) James Crisp,.NET lead for Oz ThoughtWorks Australia.

“How is time being wasted?”

“Why are stakeholders not satisfied?”

“How is money being wasted?”

“What makes the work unpleasant?”

Page 5: The Ultimate ALM Environment (circa 2010) James Crisp,.NET lead for Oz ThoughtWorks Australia.

Requirements Management

Feature Management

Page 6: The Ultimate ALM Environment (circa 2010) James Crisp,.NET lead for Oz ThoughtWorks Australia.
Page 7: The Ultimate ALM Environment (circa 2010) James Crisp,.NET lead for Oz ThoughtWorks Australia.

Source: Jeff Patton (http://agileproductdesign.com/blog/the_new_backlog.html)

Page 8: The Ultimate ALM Environment (circa 2010) James Crisp,.NET lead for Oz ThoughtWorks Australia.

[Placeholder for requirements document / process]

Source: http://www.flickr.com/photos/dblancquaert/4245076510/sizes/l/

Page 9: The Ultimate ALM Environment (circa 2010) James Crisp,.NET lead for Oz ThoughtWorks Australia.

CriteriaEncourages deferring detail

Encourages “requirement” prioritisation

See the “Tree”

Encourages less documents & cycles

Designed for information consumers

Page 10: The Ultimate ALM Environment (circa 2010) James Crisp,.NET lead for Oz ThoughtWorks Australia.

Source: Jeff Patton on Story Maps (http://agileproductdesign.com/blog/the_new_backlog.html)

Page 11: The Ultimate ALM Environment (circa 2010) James Crisp,.NET lead for Oz ThoughtWorks Australia.

Project Management

Workflow

Monitoring & Reporting

Issue Management

Page 12: The Ultimate ALM Environment (circa 2010) James Crisp,.NET lead for Oz ThoughtWorks Australia.
Page 13: The Ultimate ALM Environment (circa 2010) James Crisp,.NET lead for Oz ThoughtWorks Australia.
Page 14: The Ultimate ALM Environment (circa 2010) James Crisp,.NET lead for Oz ThoughtWorks Australia.

Source: http://www.flickr.com/photos/joiseyshowaa/2402764792/sizes/o/

Page 15: The Ultimate ALM Environment (circa 2010) James Crisp,.NET lead for Oz ThoughtWorks Australia.

The 15 minute meeting

that takes

2 weeks to coordinate

Page 16: The Ultimate ALM Environment (circa 2010) James Crisp,.NET lead for Oz ThoughtWorks Australia.

http://www.flickr.com/photos/usag_kaiserslautern/2750224436/

Page 17: The Ultimate ALM Environment (circa 2010) James Crisp,.NET lead for Oz ThoughtWorks Australia.

CriteriaExposes flow and problems

Limits work in process

Exposes clear priorities

Page 18: The Ultimate ALM Environment (circa 2010) James Crisp,.NET lead for Oz ThoughtWorks Australia.

Signed-OffAcceptanceTesting

In ProgressPlanned

Iteration Progress

Priority

Page 19: The Ultimate ALM Environment (circa 2010) James Crisp,.NET lead for Oz ThoughtWorks Australia.
Page 20: The Ultimate ALM Environment (circa 2010) James Crisp,.NET lead for Oz ThoughtWorks Australia.

1

Total scopeTre

nd

Expected Completion

Time (Iterations)

2 3 4 5 6 7 8 9 10

Actuals

Sco

pe (sto

ry

poin

ts)

Page 21: The Ultimate ALM Environment (circa 2010) James Crisp,.NET lead for Oz ThoughtWorks Australia.

Design

Modeling

Page 22: The Ultimate ALM Environment (circa 2010) James Crisp,.NET lead for Oz ThoughtWorks Australia.

Source: http://erik.doernenburg.com/2009/07/making-esb-pain-visible

Page 23: The Ultimate ALM Environment (circa 2010) James Crisp,.NET lead for Oz ThoughtWorks Australia.

“I’m glad we’re all agreed then.”

Page 24: The Ultimate ALM Environment (circa 2010) James Crisp,.NET lead for Oz ThoughtWorks Australia.

CriteriaEncourages keeping things simple

Low cost exploration of multiple options

Evidence based

Easily accessible to stakeholders

Page 25: The Ultimate ALM Environment (circa 2010) James Crisp,.NET lead for Oz ThoughtWorks Australia.

Source: http://www.flickr.com/photos/brylyn/279973066/

Page 26: The Ultimate ALM Environment (circa 2010) James Crisp,.NET lead for Oz ThoughtWorks Australia.
Page 27: The Ultimate ALM Environment (circa 2010) James Crisp,.NET lead for Oz ThoughtWorks Australia.
Page 28: The Ultimate ALM Environment (circa 2010) James Crisp,.NET lead for Oz ThoughtWorks Australia.

Testing

Page 29: The Ultimate ALM Environment (circa 2010) James Crisp,.NET lead for Oz ThoughtWorks Australia.

“[Manual] testing is our bottleneck”

-- Head of Technology, at a recent client

Page 30: The Ultimate ALM Environment (circa 2010) James Crisp,.NET lead for Oz ThoughtWorks Australia.

“Manual scripted testing should be a human rights violation”

-- Martin Fowler (http://twitter.com/martinfowler/status/2273044056)

Page 31: The Ultimate ALM Environment (circa 2010) James Crisp,.NET lead for Oz ThoughtWorks Australia.

CriteriaSupport fully automated testing

Support automation assisted testing

Easily accessible to stakeholders

Scalable & Fast

Page 32: The Ultimate ALM Environment (circa 2010) James Crisp,.NET lead for Oz ThoughtWorks Australia.
Page 33: The Ultimate ALM Environment (circa 2010) James Crisp,.NET lead for Oz ThoughtWorks Australia.
Page 34: The Ultimate ALM Environment (circa 2010) James Crisp,.NET lead for Oz ThoughtWorks Australia.
Page 35: The Ultimate ALM Environment (circa 2010) James Crisp,.NET lead for Oz ThoughtWorks Australia.
Page 36: The Ultimate ALM Environment (circa 2010) James Crisp,.NET lead for Oz ThoughtWorks Australia.

Source: http://www.flickr.com/photos/jjacek/2619935342/

Page 37: The Ultimate ALM Environment (circa 2010) James Crisp,.NET lead for Oz ThoughtWorks Australia.

Desktop

Dev

UAT

Sys Test

Pre Prod

Production

Page 38: The Ultimate ALM Environment (circa 2010) James Crisp,.NET lead for Oz ThoughtWorks Australia.

Build

Release Management

Deployment

Page 39: The Ultimate ALM Environment (circa 2010) James Crisp,.NET lead for Oz ThoughtWorks Australia.

Slow Unreliable

Inconsistent

Page 40: The Ultimate ALM Environment (circa 2010) James Crisp,.NET lead for Oz ThoughtWorks Australia.

CriteriaFully automated, visible build

Fully automated deployment

Fully automated environment creation

Support for multiple environments

Page 41: The Ultimate ALM Environment (circa 2010) James Crisp,.NET lead for Oz ThoughtWorks Australia.

Build ScriptingAnt / MS Build / NAnt

Rake / nRake

Powershell

Page 42: The Ultimate ALM Environment (circa 2010) James Crisp,.NET lead for Oz ThoughtWorks Australia.
Page 43: The Ultimate ALM Environment (circa 2010) James Crisp,.NET lead for Oz ThoughtWorks Australia.
Page 44: The Ultimate ALM Environment (circa 2010) James Crisp,.NET lead for Oz ThoughtWorks Australia.
Page 45: The Ultimate ALM Environment (circa 2010) James Crisp,.NET lead for Oz ThoughtWorks Australia.

Source: http://www.flickr.com/photos/mukluk/311712807/

Page 46: The Ultimate ALM Environment (circa 2010) James Crisp,.NET lead for Oz ThoughtWorks Australia.
Page 47: The Ultimate ALM Environment (circa 2010) James Crisp,.NET lead for Oz ThoughtWorks Australia.
Page 48: The Ultimate ALM Environment (circa 2010) James Crisp,.NET lead for Oz ThoughtWorks Australia.

Development

Version Control

Page 49: The Ultimate ALM Environment (circa 2010) James Crisp,.NET lead for Oz ThoughtWorks Australia.

CriteriaMinimise administrative overhead

Integrated Refactoring

Integrated Testing

Integrated Version Control

Page 50: The Ultimate ALM Environment (circa 2010) James Crisp,.NET lead for Oz ThoughtWorks Australia.
Page 51: The Ultimate ALM Environment (circa 2010) James Crisp,.NET lead for Oz ThoughtWorks Australia.
Page 52: The Ultimate ALM Environment (circa 2010) James Crisp,.NET lead for Oz ThoughtWorks Australia.

“Ultimate” ALM Environment

Physical workspace is deliberately designed to expose information

Automated test, build, environment creation and deployment

Supporting the creativity and interaction of people

Page 53: The Ultimate ALM Environment (circa 2010) James Crisp,.NET lead for Oz ThoughtWorks Australia.

Source: http://www.flickr.com/photos/larskflem/3262269450/

Page 54: The Ultimate ALM Environment (circa 2010) James Crisp,.NET lead for Oz ThoughtWorks Australia.

Questions ?