InfoQ Homepage Culture & Methods Content on InfoQ

Articles

RSS Feed

Newer Older

Pattern-Based Architecture Reviews

In this IEEE article, authors Neil Harrison and Paris Avgeriou discuss a pattern-based architecture review (PBAR) process to help with system-wide quality attributes. They also discuss how PBAR approach helps with agile practices like frequent releases, changes for user needs, and lightweight documentation. They illustrate the benefits of PBAR process with a real-world project.

Neil B. Harrison Paris Avgeriou
on Feb 14, 2012
10 tips on how to prevent business value risk

One category of risk that project teams need to ensure they address is business value failure – delivering a product that fails to provide value for the business investor. The authors provide insight into the underlying causes of business value risk and provide ten tips on how to avoid them.

Chris Matts Olav Maassen
on Feb 07, 2012
Your Brain on Scrum

Status, Certainty, Autonomy, Relatedness, and Fairness are wired into the human brain. Michael de la Maza how the latest neuroscience findings support agile software development and that there are good brain-based reasons why agile is so effective.

Michael de la Maza
on Feb 02, 2012
New Book: Agile Software Engineering with Visual Studio

“Agile Software Engineering with Visual Studio – from Concept to Continuous Feedback” is a new book that provides a deep-dive into the Visual Studio-TFS features, that can help Agile teams manage their application lifecycle better. It is written by Sam Guckenheimer (Product Owner, Visual Studio Strategy at Microsoft) and Neno Loje (Independent ALM Consultant and TFS specialist).

Roopesh Shenoy
on Jan 26, 2012
Dialogue Sheets: A new tool for retrospectives

Dialogue sheets allow teams to hold facilitator-less retrospectives. They promote self-organization and encourage everyone to speak in the exercise. This results in great levels of participation in and higher energy levels in teams. The sheet itself is A1 in size, 8 times larger than a regular sheet, pre printed with instructions and questions to motivation discussion.

Allan Kelly
on Jan 03, 2012
The 12 Days of Agile Christmas

In the spirit of the season we bring you the 12 Days of Christmas in Agile projects.

Terry Bunio
on Dec 23, 2011
Succeeding with Dependency Injection

While the principal pattern is easy to understand it can be difficult to succeed with Dependency Injection without considering the larger context. DI is an application of the principle of Inversion of Control and to succeed with IoC you’ll also need to invert your thinking. This article provides a sketch of the mental model you need to adopt to succeed with DI.

Mark Seemann
on Dec 19, 2011
Feature Injection: three steps to success

Often Customers provide half baked solutions with no linkage to value. An Agile team needs examples linked to the Business Value they provide. Feature Injection is a process that takes a half baked solution identifies the Business Value it provides and then produces a set of examples driven from that value.

Chris Matts Gojko Adzic
on Dec 14, 2011
Rick Kazman on Evaluating Software Architectures

Evaluating software architectures is a critical part of the software architecture lifecycle processes. The book "Evaluating Software Architectures: Methods and Case Studies" covers the software architecture evaluation topic in detail focusing on different architecture evaluation frameworks. InfoQ spoke with Rick Kazman, co-author of the book on the architecture evaluation topic.

Srini Penchikala
on Dec 13, 2011
Key Takeaway Points and Lessons Learned from QCon San Francisco 2011

This article presents the main takeway points as seen by the many attendees who blogged about QCon. Comments are organized by tracks and sessions: Keynotes, Advancing Agile to the Next stage with Lean, Agile in the Midlife, Architecture Case Studies, Beautiful Code, Big Data and NoSQL, Functional Web, Cross Platform Mobile Development, HTML5 & JavaScript, Systems That Never Stop and many more!

Abel Avram
on Dec 09, 2011
Is Agile Sub-Optimal?

Lean has the concept of a Sub-Optimal process. A Sub-Optimal process is where a part of the process is optimized to the detriment of the entire process’s efficiency. Are Agile practices creating projects that are in danger of being or becoming Sub-Optimal? What Agile practices are contributing to projects becoming Sub-Optimal? What can we do ensure our projects do not become Sub-optimal?

Terry Bunio
on Dec 05, 2011
Agile Adoption – Vital Behaviours and Influence Strategies

Steve is interested in uncovering better ways to deliver successful projects regardless of whether or not those ways are ‘agile’. After reading "Influencer, the Power to Change Anything" he found a set of behaviours and influence strategies that are helpful for giving projects the best chance for success and also for helping teams transition to agile.

Steve Rogalsky
on Dec 01, 2011

Newer Articles

Older Articles

InfoQ Software Architects' Newsletter

Articles