• submit to reddit
Roman Pichler03/12/14
3393 views
0 replies

A Template for Formulating Great Sprint Goals

I find it helpful to consider three questions when choosing a sprint goal: Why do we carry out the sprint? How do we reach its goal? And how do we know that the goal has been met? My sprint goal template therefore consists of three main parts: the actual goal, the method employed to reach the goal, and the metrics to determine if the goal has been met.

Dalip Mahal03/12/14
11648 views
7 replies

The Programmer Productivity Paradox

If the average programmer writes about 50 lines of production code a day. A 50,000 line program would take 1,000 man days to produce. The 50,000 line listing can be entered by a programmer at about 1,000 lines a day or about 50 man days. So what the heck are the developers doing for the other 950 days?

Andrew Fuqua03/11/14
5006 views
0 replies

Don’t Estimate Software Defects

I don’t estimate software defects. Well, I have two exceptions: If I have a backlog of old defects to burn down, I may estimate those. If I have found some new bug that we plan to fix in some later sprint, I may estimate those (though I really don’t like to defer defect fixes). Otherwise, I don’t estimate defects.

Michael Heinrichs03/11/14
3644 views
0 replies

3 Reasons to Choose Vert.x

The application platform Vert.x takes some of the innovations from Node.js and makes them available on the JVM, combining fresh ideas with one of the most sophisticated and fastest runtime environments available. Vert.x comes with a set of exciting features that make it interesting for anybody developing web applications.

Vlad Mihalcea03/11/14
4332 views
0 replies

Choosing a Leader like an Agilist

We need to trust our teams and respect their opinions. I like this approach since it’s a very good way of spotting leaders that you weren’t aware of. People with leadership potential are rare gems and I always stay open-minded to any method that can bring me the next great leader.

Tom Howlett03/10/14
6816 views
2 replies

The Day I Met a Customer

Like many developers, I’ve been protected from apparently difficult customers by my managers and left to get on with the important job of “writing code”. But this week I left our office and headed out to a technology park to work directly with one of our customers, and after a couple of days of understanding each others needs I’ve rarely felt so excited about “writing code”, because I know it will be valued.

Anders Abel03/10/14
2405 views
2 replies

International Women's Day and the Software Industry

This past Saturday was international women’s day (IWD). A day that should make us men in the software industry think about why so few women study CS and why so many of those who did, never establish a career in the industry. What do we men do wrong, when women don’t feel welcome?

Alec Noller03/09/14
3531 views
0 replies

The Best of the Week (Feb. 28): Big Data Zone

Make sure you didn't miss anything with this list of the Best of the Week in the Big Data Zone. This week's best include the release of Apache Hadoop 2.3.0, Big Data on the precipice of a collapse, the second edition of "Hadoop in Practice," and more.

George Dinwiddie03/07/14
5635 views
0 replies

What does it mean for an estimate to be right?

If we choose conformance to actuals as the definition for the “rightness” or “goodness” of an estimate, we’re certainly encouraging overestimation. It’s easier to overestimate and then waste effort as needed to be “accurate” than to underestimate and try to hit a possibly impossible target. Those who ask for estimates using this definition know this, so they are likely to arbitrarily cut the estimate in order to put pressure on development and prevent padding.

Chris Haddad03/07/14
6797 views
0 replies

DevOps = DevOps Principles + DevOps Practices

Successful, long-lasting movement have a clear manifesto outlining goals and principles. Many DevOps adopters may not be aware of the DevOps Manifesto (created by Jez Humble @jezhumble) nor how successful DevOps requires keeping a clear focus on principles, practices, and value (instead of infrastructure tooling).

David Green03/07/14
11386 views
11 replies

Why shouldn't I test private methods?

Why shouldn’t you test private methods? Because the fact you’re asking the question means the method shouldn’t be private – it’s a piece of independent behaviour that warrants testing. The hard choice, the design decision, is where you stick it.

Avishek Sen Gupta03/06/14
5492 views
0 replies

Advice for the New Tech Lead: The Realities of Distributed Development

Let’s face it; not everyone has been there and done that, when it has come to Distributed Development. And if you have, there is a high probability that you were probably in a distributed team, you mostly worked with one group or the other, but not both. These words I will probably keep repeating in the future, but I’m not apologising for them: Never be Complacent.

Alec Noller03/05/14
9025 views
0 replies

Dev of the Week: Matt Butcher

Every week here and in our newsletter, we feature a new developer/blogger from the DZone community to catch up and find out what he or she is working on now and what's coming next. This week we're talking to Matt Butcher, Lead Cloud Engineer at Revolv, Inc, author, and teacher at Loyola University Chicago.

Benjamin Ball03/05/14
10686 views
0 replies

DZone Weekly Link Roundup (March 5)

This week in the link roundup: Intel joins the smartwatch arms race with a $100M purchase, Facebook looks to go into low-orbit, Flexcoin shuts its doors, PHP gets a renaissance, a programmer finally admits his limitations, we learn that God created the universe on Rails, and Jurassic Park comes to your browser.

Mike Cottmeyer03/05/14
6724 views
0 replies

Don’t sell me agile, solve my problem

A wise, retired CIO told me, “Don’t sell me your solution, solve my problem.” That statement further solidified my belief that I am not “implementing agile” (hang with me), but rather I am solving a problem or a set of problems that commonly occur in enterprise environments.