Tag Archives: sdlc

Strategies for Scaling Agile Development

Towards agile architecture
Architecture throughout the lifecycle
Who is responsible for architecture?
Have an “architecture owner” role
Agile architecture at scale
Base your architecture on requirements
Model your architecture
Consider several alternatives
Remember enterprise constraints
Travel light
Prove your architecture with working code
Communicate your architecture 
Think about the future, just wait to act (defer commitment)
Take a multi-view approach
How does this work?
Who is actually doing this?
Addressing the myths around agile and architecture

(Full Story: Strategies for Scaling Agile Development)

Strategies for Scaling Agile Development

  1. Towards agile architecture
  2. Architecture throughout the lifecycle
  3. Who is responsible for architecture?
  4. Have an “architecture owner” role
  5. Agile architecture at scale
  6. Base your architecture on requirements
  7. Model your architecture
  8. Consider several alternatives
  9. Remember enterprise constraints
  10. Travel light
  11. Prove your architecture with working code
  12. Communicate your architecture
  13. Think about the future, just wait to act (defer commitment)
  14. Take a multi-view approach
  15. How does this work?
  16. Who is actually doing this?
  17. Addressing the myths around agile and architecture

(Full Story: Strategies for Scaling Agile Development)

Closing a Few Doors: Software Requirements Gathering

Wow, the parallels in Dr. Ariely new book “Predictably Irrational” to the Software Requirments Gathering process are unintentional but powerful.

“Xiang Yu was a Chinese general in the third century B.C. who took his troops across the Yangtze River into enemy territory and performed an experiment in decision making. He crushed his troops’ cooking pots and burned their ships.

He explained this was to focus them on moving forward — a motivational speech that was not appreciated by many of the soldiers watching their retreat option go up in flames. But General Xiang Yu would be vindicated, both on the battlefield and in the annals of social science research.

He is one of the role models in Dan Ariely’s new book, “Predictably Irrational,” an entertaining look at human foibles like the penchant for keeping too many options open. General Xiang Yu was a rare exception to the norm, a warrior who conquered by being unpredictably rational.

Most people can’t make such a painful choice, not even the students at a bastion of rationality like the Massachusetts Institute of Technology, where Dr. Ariely is a professor of behavioral economics. In a series of experiments, hundreds of students could not bear to let their options vanish, even though it was obviously a dumb strategy (and they weren’t even asked to burn anything).

The experiments involved a game that eliminated the excuses we usually have for refusing to let go.. In the real world, we can always tell ourselves that it’s good to keep options open.

You don’t even know how a camera’s burst-mode flash works, but you persuade yourself to pay for the extra feature just in case. You no longer have anything in common with someone who keeps calling you, but you hate to just zap the relationship.”

How many of us have fought business analysts who want ‘everything configurable’ and to deploy ‘every feature’? Frankly, I can’t think of any bigger timesink for software teams these days.

See the full article and NYT review at: The Advantages of Closing a Few Doors – New York Times


Follow

Get every new post delivered to your Inbox.