• submit to reddit
James Shore06/02/14
0 replies

The Lament of the Agile Practitioner

See, 2-5 years is about how long a not-really-Agile Agile team can survive before things shudder to a complete halt.

Whitney Baker06/01/14
0 replies

The Best of the Week (May 23): Agile Zone

Make sure you didn't miss anything with this list of the Best of the Week in the Agile Zone (May 23 to May 30). Topics include chronic stress, Parkinson's Law of Triviality, the importance of developers, adjustable standing desks and employee value.

Antonin Januska05/31/14
4 replies

Bro, do you even program? The case of non-programming programmers

It was late at night, when I stumbled on yet another Quora question concerning the topic of “Programmers not programming”. The topic itself always seemed ridiculous to me. What is a programmer if they can’t program?

Rob Galanakis05/30/14
0 replies

There is no essence of Agile

I don’t know where the idea that Agile can be distilled down into one or two practices or principles comes from. Thinking this way is extremely harmful.

Mike Cottmeyer05/30/14
0 replies

Converting Feelings to Metrics with a “Safety Check”

In the quest to understand how the delivery teams feel about changes in delivery process, a simple tool called the “Safety Check” can be used to measure how empowered the team feels.

Chris Odell05/30/14
0 replies

Code Reviews Are A Luxury, So Cherish Them

When working as an in-house developer you will have colleagues to bounce ideas off. If you have an idea, talking it over with someone can enhance it, or stop you making a less than optimal design decision. A SOHO Developer does not have this option.

Swizec Teller05/30/14
0 replies

(ab)Using d3.js to make a Pong game

D3.js is a data visualization library first and foremost. That’s what people use it for. To make shiny things that blow everyone’s minds. Recently I made a simple game of Pong using D3. There really isn’t much to making a game like this with D3.

Johanna Rothman05/29/14
0 replies

Scaling Agile? Think Out, Not Up

When you think scaling agile, think out, not up. You use small world networks, and when you say, “think out, not up,” it’s a very nice catch-phrase.

George Dinwiddie05/29/14
7 replies

Another Two Sides to Estimation

Everyone in the business of software development has had experience with wanting estimates, being asked for estimates, or both. That experience frames how they look at the issue. A considerable share of those experiences have been painful.

Mike Bushong05/29/14
0 replies

The Complexity of Queueing in Modern Switches

Any time a switch needs to make a queueing decision, it makes a priority decision based on the policy you have instructed it with. The amount of queues, the de-queueing strategy, the depth of the queues, drop priority, and everything else associated with queueing creates a “one packet is more important than another” choice.

Roman Pichler05/29/14
0 replies

10 Tips for Creating an Agile Product Roadmap

A product roadmap is a powerful tool to describe how a product is likely to grow, to align the stakeholders, and to acquire a budget for the product. But creating an effective roadmap is not easy particularly in an agile context where changes occur frequently and unexpectedly.

Anh Tuan Nguyen05/29/14
0 replies

Software Development and Newton's Laws of Motion

I have no idea since when the word velocity found a new home in software development, it is nevertheless popular these days. However I am pretty sure that Mr. Isaac Newton would not be happy if you talk about motion without mentioning his laws.

Chris Haddad05/29/14
0 replies

The Agile DevOps PaaS Mindset

Adopting agile devops requires a structural mind shift, and successful IT teams follow manifesto guidance to change delivery dynamics, take small steps to build one team, focus on real deliverables, accelerate reactive adaptation, and guide continuous loop activity.

Whitney Baker05/28/14
0 replies

DZone Weekly Link Roundup (May 28)

This week's topics include a new Firefox OS developer phone, Googlebot improvements, a new version of perl, diving into git, the balance between software and hardware in product development, physics and philosophy in information, and some fun-spirited projects including a drink-making robot and dogescript.

Julian Exenberger05/28/14
6 replies

When too much coding can kill you.

Well it's true: too much coding can kill you, the real question is "what is the reason?" and the answer to that is; Chronic Stress.