• submit to reddit
Geert Bossuyt02/22/11
0 replies

Exercises for understanding Agile

I regularly run workshops to highlight certain aspects of an agile way of working and to help participants achieve a deeper understanding of these topics. I would like to share two of best received workshop sessions with you so that you can run them too....

James Shore02/21/11
1 replies

A Hardheaded View of TDD

I had a chance to pair with Llewellyn Falco last week at Agile Open Northwest. Our approaches to test-driven development are pretty different, so we had some interesting conversations on the nature of TDD. In a followup email, Llewellyn said that his...

Mitch Pronschinske02/21/11
1 replies

"Nerd Herder" Cal Evans Teaches Devs Career Strengthening Skills

Cal Evans is a DZone MVB and a self-proclaimed "Nerd Herder."  He has 10 years experience in building dynamic, data-driven, interactive web sites based on the LAMP stack, but these days he's interested in teaching developers about the things you...

Mark Needham02/21/11
0 replies

Pomodoro: Observations from giving it a go

I learnt about the pomodoro technique a couple of years ago and while I did try it out sporadically back then, it’s only recently that I thought I’d properly give it a try when managing my spare time. My approach without the pomodoro technique is to...

Giorgio Sironi02/20/11
0 replies

Practical PHP Testing Patterns: Automated Teardown

The idea behind the Automated Teardown pattern is to keep track of all resources of a certain kind (like sockets, or database connections, or opened files), in order to perform an automatic release after the tests have terminated.Remember that teardown is...

Robert Diana02/18/11
1 replies

Design From The User Perspective

Traditional requirements gathering tends to focus on the data inputs, business requirements and data outputs. Obviously, in order to have a system that functions correctly and reliably, these needs must be met. However, in traditional software development,...

Dror Helper02/17/11
0 replies

Multiple asserts – done right

If you’ve been writing unit tests for some time or seen a good presentation on how to write unit tests you probably heard the “One assert per test” rule. There are real benefits in having only one assert in each tests – you get a focused tests,...

Geert Bossuyt02/17/11
1 replies

MoreAgile Principles

MoreAgile organizations support the following principles : Complexity is a choice; we choose simplicity. We carry out our vision and strategy so that our people can make decisions in line with the mission of our organization. Effectiveness is worth...

Mark Needham02/17/11
3 replies

Increasing team sizes: Collective unresponsibility

After a few recent conversations with colleagues as well as my observations of several projects I’m coming to the conclusion that the way that people react in situations often differs significantly depending on whether they’re working in a large or...

Giorgio Sironi02/16/11
0 replies

Do not fear the command line

As you know I love ssh, but I also love the command line tools  in general.

Michael Norton02/15/11
1 replies

Telling the complete 'Story'

Decomposing the story formatWorking with several clients, I see differing story formats. The format I see most recommended is "As a, I want, So that".  The format I see most utilized is "I want". Isn't this the important part of the...

Giorgio Sironi02/15/11
0 replies

Practical PHP Testing Patterns: Garbage-Collected Teardown

In order to perform tests, you create fixtures such as the System Under Test and input or output data. Usually this fixtures are just objects.Garbage collection, a mechanism present in many languages, deletes objects and variables (and thus fixtures) when...

James Sugrue02/15/11
0 replies

Prediction #4: The single vendor ALM stack becomes extinct in organizations with more than two developers

This is a reposting from Mik Kersten's Tasktop Blog.  Look for more predictions in this series on his blog and on Agile Zone

Mike Cohn02/14/11
3 replies

Reflections on the 10 Years Since the Agile Manifesto

Today is the tenth anniversary of the start of the meeting that resulted in the Agile Manifesto. Much has changed in the ten years since the Agile Manifesto. Back then, the processes encompassed by the Manifesto—Extreme Programming, Scrum, DSDM,...

James Shore02/14/11
1 replies

Proficiencies of Planning

With our Art of Agile Planning training course coming up at the end of the month, Diana Larsen and I met for our normal pre-course review and revision. We had tried teaching the material top-down and bottom-up, and both ways caused confusion in the early...