News for hackers. Stuff that matters.
Re:It’s not the methods that are Agile, it’s the people by ryandrake on Tuesday November 22, 2016 @12:06PM (#13015497)
Here are a few problems with your football team analogy:

1. The football team that has the knowledge and judgment you described are all A-players. A-players tend to not need a lot of process. One of the reasons we have project management and software methodologies and all that process is to help the team's B- and C- players perform predictably and consistently, if not close to as good as the A-players. If you actually found that mythical group of software people where each and every one of them knew the business in as much depth as your football players do, then yes, they probably wouldn't need as much structure. My experience has been these teams are extremely rare.

2. A football game is physically observable at all times by all stakeholders. Status needs no reporting. The score is known to all. The position of the ball is known to all. This is not true for software projects. Part of project management is providing visibility to stakeholders and leadership so that risk can be managed and informed strategic decisions can be made. This is why "Agile" emphasizes delivering working software as milestones. Different project management schemes use different methods to track and report status, but the end goal is the same.

3. A football game is already time boxed due to the structure of the game. There is a start time and a duration, it's separated into quarters, team activities are structured into downs, which aids the team in making tactical and strategic decisions. How would all these smart players "know precisely what to do" if they didn't know what quarter it was or how much time was left on the clock? Software does not naturally have any of this structure, so various methodologies seek to frame project with structure to aid decision making.

4. You really don't think any football team's leadership ever yells "We gotta get at least 10 more by halftime go make it happen!" You have to have intermediate milestones. Every sport I've ever played has had a coach or lead player barking the current goals at me. Guess what: That's part of the machine's oil.

Re:It’s not the methods that are Agile, it’s the people by jay_kyburz on Tuesday November 22, 2016 @04:20PM (#13017775)
Actually, in my mind you helped strengthen the football team analogy.

1. I only like to work with A players as well. Only hire A players. If you have B and C players, let them go and keep looking.

2. Yes, working software is observable to all. When you have working software, everybody knows what the score is and where the ball is. If you software sux, the ball is in the wrong end of the field.

3. Many software projects have the same time constraint. A conference it needs to be ready by, or a point in time where there is no money left.

4. Yeah, thats the job of the team lead.

Re:It’s not the methods that are Agile, it’s the people by TeMPOraL on Tuesday November 22, 2016 @01:41PM (#13016345)
I'd add two more problems:

5. Football is a zero-sum PvP game, programming is a PvE race-the-clock game. In football, you don't have to be good, you just have to be not worse than other team (+/- luck factor). In programming, you have random obstacles (requirements, management decisions) thrown at you, the effort it takes to scale those obstacles is mostly unpredictable, and you're being pushed to do it before deadline "or else".

6. Timescale. American football match takes an hour (1.5 hour for soccer, + break). That's how much time the team works together until the next deliverable. In programming, it's weeks or months. Sustaining teamwork on such a long scale is a completely different task. If you want to compare something to football, look at hackatons - and then you'll see people who worked together before often excel at getting things done.

Re:It’s not the methods that are Agile, it’s the people by RandomOpinion on Tuesday November 29, 2016 @10:43AM (#13063691)
Re: #1, that kind of depends. Are the B- and C-players at that level because they are incapable or because they've never been shown how to be A-players? If the latter, a well-bonded team can motivate and teach them how to become an A-player as well.