InfoQ Homepage Agile Content on InfoQ

Articles

RSS Feed

Newer Older

Agile Development Team Charter

Project Charters have rightfully focused on scope & goals for the project. However, team members can be unclear on their roles, activities, and expectations. This is especially true for people new to Agile. The Agile Development Team Charter addresses this gap by reviewing the Agile Prime Directive, Incremental Innovation Statements, and Team Member User Stories to provide clarity and context.

Terry Bunio
on Feb 27, 2012
Faster, Better, Higher – But How?

One of the main challenges when designing software architecture is the consideration of quality attributes. Not only their design turns out to be difficult, but also the specification of these attributes. Consequently, many problems in software systems are directly related to the specification and design of quality attributes such as modifiability or performance, to name just a few.

Michael Stal
on Feb 20, 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 Rise of Application Analytics: A New Game Demands New Rules

When developers know how their applications are really being used “in the wild,” they will build better software, more efficiently, and with greater confidence. Sebastian Holst shows you how using application analytics.

Sebastian Holst
on Dec 27, 2011
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
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
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
Trust is good, Control is better - Software Architecture Assessment

Testing is an important means to obtain information about implementations. Likewise, code reviews help to keep the code quality high. What is very common for code, gets sometimes neglected for software architecture. But how can a project team test the architecture itself? Software architecture assessment represents an effective approach for introspecting and assessing software design.

Michael Stal
on Nov 29, 2011

Newer Articles

Older Articles

InfoQ Software Architects' Newsletter

Articles