BT

21st Century Software Delivery with Jez Humble

by Daniel Bryant on  Feb 11, 2015

Jez Humble has stated that current software delivery practices are not optimised to create valuable software, and three issues must be addressed in order to enable innovation. First, the traditional project model is unsuitable. Second, the entire organisational value stream must be addressed. Third, the problems are rooted in process and culture, not organisational structure or tooling.

Evidence-Based Managing of Software Development

by Ben Linders on  Jan 29, 2015

If organizations want to make informed management decisions to maximize the delivered value they will need to gather evidence about value says Gunther Verheyen. InfoQ interviewed Gunther about evidence based software management and finding evidence, how Scrum relates to evidence-based managing, challenges in scaling agile, and advice for enterprises that want to adopt Scrum.

Agile Adoption with the Agile Fluency Model

by Ben Linders on  Jan 28, 2015

In too many cases agile is failing to deliver on its promise says Steve Holyer. At the OOP 2015 conference Steve explained how we can choose the rewards and benefits that we want to get out of agile development and plan the investments to achieve them. He presented the agile fluency model and explored a solution-focused approach for organization to find their path in adopting agile.

Q&A with Gerald Weinberg on The Influence of Individual Moods on Team Working

by Ben Linders on  Dec 11, 2014

InfoQ is researching the factors that influence the mood of teams. As team mood is an aggregation of the individual moods of team members, understanding the individual mood and how it influences team working can help to learn more about team moods. InfoQ interviewed Gerald Weinberg about individual and team mood, influencing the mood of individuals and discussing moods in teams.

Knowing if You Are Building the Right Product

by Ben Linders on  Jul 10, 2014

Developing and delivering products which customers don’t want and for which there is no market can be costly. Agile can help you to efficiently develop products, but you need to know what to build. How can you find out which products your customers need?

Balancing Experiments and Deliveries in Product Development

by Ben Linders on  Feb 06, 2014

Experimentation using for instance lean startup can help you learn about your customers and find out which features and product would be valuable. The value however comes from building products and actually delivering them to customers. You need to find ways to balance between experimentation and delivery.

How Swarming Helps Agile Teams to Deliver

by Ben Linders on  Feb 28, 2013

Swarming is a technique that helps agile teams to deliver working software fast and frequently. What is swarming, what are the benefits of swarming, and when and how to apply it?

Presentation: Making Apps That Don't Suck

by Michael Floyd on  May 25, 2011 13

Developing apps that surprise and delight can seem like an illusive goal that is difficult to articulate or quantify. But in this latest presentation just posted on InfoQ Mike Lee, the software engineer that worked on projects like Delicious Library,Tap Tap Revenge and the Obama ’08 iPhone app, proposes an algorithm for making better apps.

How to Convince the Product Owner to Prioritize the Backlog?

by Dan Puckett on  Dec 13, 2010 4

Scrum works most effectively with a prioritized product backlog. Prioritizing the backlog is part of the product owner role, but what can you do when your product owner won't prioritize the backlog because he or she doesn't see the value in prioritization?

Agile Architecture - Oxymoron or Sensible Partnership?

by Shane Hastie on  May 14, 2010 9

A number of commentators have been talking about the perceived dichotomy between Agile techniques and architectural thinking. This post investigates some of the tensions between Big Up Front Design (BDUF) and You Aint Gonna Need It (YAGNI) thinking and looks at how the two approaches can in fact work together in complimentary ways.

Harmonizing Agile With "User-Centered Design"

by Mike Bria on  Mar 17, 2010 6

UX specialist Anthony Colfelt presents a case for how agile, alone, might not be sufficient and a thorough and engaging look into how User-Centered Design can, and should, be merged with it.

Emerging Industry SOA Best Practices

by Boris Lublinsky on  Mar 10, 2010 4

A new MITRE whitepaper documents a variety of best practices and key characteristics for a successful SOA implementation.

Continuous Deployment, In Practice

by Mike Bria on  Jan 27, 2010

Continuous deployment has gained a recent buzz in the Lean-slanted "eliminate work-in-progess" movement. But while many may find this an intriguing and logically worthwhile objective, many less can visualize how this might actually be achieved. Ash Maurya helps to fill this gap by describing his experience with making it happen at his company.

Estimating Business Value

by Chris Sims on  Jan 04, 2010 2

The traditional agile approach to prioritization is that user stories of higher business value should be implemented before ones of lower business value. The concept is simple, but implementing it well relies on having a mechanism to assess business value. Pascal Van Cauwenberghe has recently described an approach to defining business value, called "Business Value Modeling", which may help.

Refactor or Rewrite?

by Vikas Hazrati on  Nov 24, 2009 10

The goal of refactoring and rewriting is to improve the sanity of the system by improving the code readability, structure and clarity. A clean code would be easier to maintain and enhance. However, on many occasions Agile teams have a tough time deciding between the two.

General Feedback
Bugs
Advertising
Editorial
InfoQ.com and all content copyright © 2006-2015 C4Media Inc. InfoQ.com hosted at Contegix, the best ISP we've ever worked with.
Privacy policy
BT