Agile Otter Blog
Tim Ottinger’s thoughts on software development.
Who (the heck) Am I?
biography
agile otter
tim ottinger
specialties
skills
history
abilities
Q and A on Velocity, Part IX
effectiveness
relationships
efficiency
productivity
management
10x
profluence
modern agile
velocity
communication
duplication
Improve Your Unit Testing 12 Ways
QA
testing
automated testing
code quality
unit test
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
The Poo-shoe Effect
unfortunate
punishment
unwanted roles
software
best you can do
helping
poo-shoe
serving
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
Working Well Enough: the Four Questions
great teams
coaching
continuous improvement
team-based work
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
Your Transition Isn’t Very Agile
process
consulting
learning
coaching
incremental
agile
transition
Dave Coplin Reimagines The Office
thinking for a living
Office
distraction
constant partial attention
teams
safety
open office
cubicles
Christopher Avery and The Responsibility Process (vid)
psychology
responsibility
obligation
justify
blame
avery
coaching
organizational psychology.
Getting Through To Each Other
thinking for a living
self-mastery
mental model
cognitive skills
frustration
communication
thinking
Why Your Code Has So Much Duplication
C#
dataflow.
dotnet
clarity
refactoring
signal:noise
clean code
maintenance
The Good Guilt Trip
shame
guilt
social
responsibility
thinking
manipulation
Process Improvement Principles
process
agreements
simplicity
discipline
improvement
anzeneer
pull
continuous improvement
safety
coaching
agile
anzen
Defending Scrum Against Stupid Arguments
apologetic
methods
adapt
retrospectives
grumpy
tranparency
planning
inspect
scrum
arguments
meetings
agile
criticism
anzen
Complicated Conversations Considered Keystone Hazards
converations
keystone hazard
dysfunctions
scarf
agreements
threats
anzen
confrontation
Purist, Pragmatist, Iconoclast, Egotist
delivery
iconoclast
bias
egotist
purist
anzen
pragmatist
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
Agile and Waterfall: More Different Than You Think
planning
management
waterfall
agile
uncertainty
agile at scale.
Bug Teams v. The Nature Of Defects
pair programming
teams
management
defects
decisions
learning
thinking
programming
Asking the Wrong Questions
process
classic
management
helping
waterfall
scrum
agile
communication
TDD: more to know
pair programming
microtest
tdd
testing
refactor
unit test
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
It Can Still Be Awesome…
geek joy
dehumanizing
software craft
enjoying
building
dystopia
joy
happiness
flying
it can be awesome
agile
humanity
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
Continuous Improvement Book
leanpub
ebook
continuous improvement
scrum master
techniques
scrum
agile coach
self improvement
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
Robert Probst and the Cubicle Wars (we lost)
cyberman
dr who
dehumanizing
herman miller
cubicles
probst
A LeanPub book for Scrum Masters?
scrum masters
ebook
teams
scrum master
multitasking
agile in a flash
book
retrospective
scrum
agile
There is no good way to eat soup with a knife.
organizational theory
agile coach
agile
management
agile manager
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
Simple v. Complicated
code virtues
craftsmen
concise
simplicity
software quality
software craft
simple design
programming
theory
quality
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
Retrospectives: What was that about hats, again?
attentive work
becoming
learning organization
guided experience
affective style
retrospective
extreme feedback
agile
information radiators
Fish Among Kangaroos: A Leadership Failure Tale
rant
mindset
becoming
meddling
Motivation
learning organization
Demotivators
change
respect
Really TDD-ing: Less simple than you think
microtests
coding
teams
software
refactoring
technical practices
tdd
enterprise
agile
distributed version control
The Power of an Agile Mindset
seeming
Linda Rising
mindset
becoming
affective style
learning
being
self improvement
respect
dysfunction
fears
failure
agile
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
Agile Coaching Camp wrapup
accus
agile coach
Coaching Camp
agile in a flash
Agile Coach Camp U.S. - Saturday (#accus)
crispin
agile coach camp
agile coach
agile
dinwiddie
columbus
The Build is Broken, Now What?
continuous integration
teamwork
build
version control
testing
agile
cooperation.
Pycon: Examples of Atrocity in Python Programming
python
clean code
failure
programming
naming
Ambient Annunciators
continuous integration
attentive work
tim ottinger
extreme feedback
information radiators
feedback
jim hood
build
jenkins
ambient annunciator
programming
informative workspace
How Do Scrum Masters Know?
feedback
scrum
scrum masters
agile
Learning from bad examples
python
failure
clean code
error
programming
duplication
Poop: The Refactoring Method
clean code
refactoring poop method comment cleanup
getting things done
fear
Free, Cheap, Scheduled: retrospective technique
schedule
learning organization
scheduled
change
retrospective
scrum
agile
free
cheap
Pairing Styles
pair programming
teamwork
scrum
objections
agile
programming
Microtesting Python Album
microtests
python
guided experience
tdd
eLearning
programming
Short Reach Revived
yesterdays weather
techniques
short reach
agile
practices
iterations
“Managing” Velocity
faster development
teams
sprints
velocity
agile
speed
World’s Shortest Agile Summary
summary
elegance
ottinger
concise
levinson
agile
dinwiddie
The Great Giveaway Begins
meetings
free
chicago
agile in a flash
user groups
Pairing, Competence, and Recognition
evaluations
skill development
unequal
objections
learning
self improvement
respect
fears
feedback
pair programming
teamwork
rockstars
agile
Meddling, Oversight, and Agile, Oh My!
agile coach
oversight
meddling
failure
agile manager
Linear and Radial Progress: Take The Next Step
code virtues
the next step
linear
craftsmen
code
great teams
habitability
refactor
radial
refactoring
clean code
agile
Platitudes Of Doom
delivery
working harder
faster
Motivation
productivity
pressure
Code Perturbation and Extensive Branch Mods
clean code
refactoring
branching
version control
perturbation
Pork Barrel Agile Failure
ottinger
pork barrel
stories
gold-plating
overdesign
agile
customer
Code Doesn’t Lie
python
clean code
pylons
tutorials
programming
Bash coolness
clever code
cool
linux
bash
variable replacement
shell programming
expansion
James Grenning boils it down
features
fluid development
elegance
clean code
business value
value
Fear of Changing Code
rewrites
refactoring
management
clean code
diffs
technical debt
fear
Raspberry Jam
tim ottinger
agile
interruptions
multitasking
raspberry jam
START
start
daunted
intimidated
procrastination
getting things done
Branching as a Coping Mechanism
agile
priority
branching
version control
dysfunction
Move from ObjectMentor
object mentor
xp
tim ottinger
agile coach
agile
textura agile practices
agile manager
No matching items









































