Agile Otter Blog

Tim Ottinger’s thoughts on software development.

Who (the heck) Am I?

biography
agile otter
tim ottinger
specialties
skills
history
abilities

Principles for Large Organizations

agile at scale
developers
scale
Scaled Scrum
Big Companies
SAFe
Rules
Corporate Culture
Principles
Scaling
agile
managers
Culture
large company

Making Data Relationships Obvious

explicit code
test
microtest
obvious relationships
clean code
intention

We Value Things On The Left More….

tools process
agile tools.
collaboration
takeBackAgile
agile manifesto
interaction
value
take back agile

The BS Line

responsibility
testing
retrospective
code review
self-awareness
agile
improvement
mastery

Writing the BDDs… Good Lord, NO!

sounding stupid
bdd
morons
dumb things people say
bad grammar
language
behavior driven development
software hicks
abusing language
writing BDDs
BDDs

Too Many Developers?

agile at scale
teams
hiring
swarming
scale
too many developers
technical debt
staffing
large scale
large teams
10x developer
agile
cooley

Otter’s Law

teams
control.
cargo cult
profluence
transformation
corporations
responsibility
learned helplessness
safety
anhedonia
xp
scrum
otters law
methodology
team-based work
take back agile

Preplanning Poker: Is This Story Even Possible?

defer
cards
explore
accept
preplanning poker
story size
estimation
feature splitting
agile games
split
reject
planning poker
story splitting
agile

Process Improvement Principles

process
agreements
simplicity
discipline
improvement
anzeneer
pull
continuous improvement
safety
coaching
agile
anzen

3 Ways We Can Revive Agile

shared learning
spread the word
blogging
build
movement
evangelize
take back agile

I Want Agile Back

agile at scale
standup meetings
projects
technical practices
iterations
angst
deathmarch
scrum
coaching
sprints
agile
take back agile
sick of agile

Scrum Managers: are they the worst?

xp
scrum
manager
management

Working Agreements

agreements
shared learning
learning organization
teamwork
debian

The Interplay of Failure, Learning, and Options

risk management
failure
options
learning
agile
iterative design

Three Steps to Safer Development

continuous integration
build server
faster
code
management
testing
tech safety
agile
software quality
technical debt
Lean Startup

Tests and Immersion in Code: The relationship

python
sniffer
software
observation
CI
testing
interoperating
ATDD
autotest
ruby
slow tests
build server
test faster
productivity
tdd
immersed
programming

Wallas’ Four Stages of Creative Thought

enlightenment
incubation
verification. Programming
stages of creative thought
agile
theory of productivity
graham wallas
preparation

Invisibility of Process, Visibility of Results

extreme programming
running tested features
say:do
metrics
theory of productivity
information radiators
programming
managers
informative workspace
agile manager

The Best Job They Know How To Do

shared learning
domain knowledge
prime directive
requirements
best you can do
retrospective
understanding
agile
theory of productivity
communication

Hoarding Knowledge: sharing enhances productivity

theory of productivity
silo
programming
agile manager

Product Health Rules!

microtests
build
tdd
testing
distributed version control
agile at scale.
large scale agile
distributed teams

Circling the Drain/Facing the Truth

continuous integration
attentive work
becoming
change
agile coach
fair
feedback
learning organization
agileinaflash
agile in a flash
agile
intimidated

Not Fair

ottinger
abuse
psychology
bad guys
cognitive bias
arguments
assholes
fair
good guys

Save(d) The Art Of Thought!

organizational theory
unavailable
book
philosophy of art
activism
classic
ebook
psychology
learning organization
art of thought
rare book
graham wallas

14 Weird Observations About Agile Team Velocity

development
yesterdays weather
stories
management
scrum master
scrum
agile coach
agile
programming
iterations
agile manager

Rewards and Performance Revisit

evaluations
Demotivators
enterprise
change
Esther Derby
dysfunction
incentives
management
performance reviews
ranking
performance management
team-based work

Empathy and Experience: Coaching

context
weinberg
agile coach
present-tense
pickle

Chickens with a Pig Complex?

chicken
teams
software
teamwork
management
roles
scrum
agile
pig

Affording Agile (Emotionally)

pair programming
daunted
learning organization
Demotivators
skill development
agile coach
clean code
agile
cooperation.

The First Puzzle Challenge

attentive work
development
teams
multitasking
retrospective
agile coach
feedback
learning organization
guided experience
teamwork
agile
tasks

Ambient Annunciators

continuous integration
attentive work
tim ottinger
extreme feedback
information radiators
feedback
jim hood
build
jenkins
ambient annunciator
programming
informative workspace

Learning from bad examples

python
failure
clean code
error
programming
duplication

Scrum Master Duties

development
agile
scrum master
tasks

Code Perturbation and Extensive Branch Mods

clean code
refactoring
branching
version control
perturbation

Python Pimpl Pattern

python
pimpl
time
fizzbuzz
strategy
No matching items