InfoQ Homepage Culture & Methods Content on InfoQ
-
/articles/communicate-business-value-stakeholders/en/smallimage/article logo.jpg)
Communicate Business Value to Your Stakeholders
Often project leaders—even Agile project leaders—talk about their projects in terms of features. Yes, and what do features really mean for stakeholders? Features are what your system or process can do. Benefits are why people care. And benefits equal business value. Learn why and how to communicate benefits rather than features—and what it will mean for you, your team and your organization.
-
/articles/agile-development-team-charter/en/smallimage/articlelogo.jpg)
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.
-
/articles/cert-secure-coding-standard/en/smallimage/book cover.jpg)
Interview and Book Review: The CERT Oracle Secure Coding Standard for Java
"The CERT Oracle Secure Coding Standard for Java" book covers the rules for secure coding using Java programming language and its libraries with the goal to help Java developers eliminate insecure coding practices that can lead to vulnerable code. InfoQ spoke with book authors about how the security rules discussed in the book compare to other security coding frameworks.
-
/articles/ieee-pattern-based-architecture-reviews/en/smallimage/logo.jpg)
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.
-
/articles/10-tips-prevent-business-value-risk/en/smallimage/red rose.jpg)
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.
-
/articles/brain-scrum-maza/en/smallimage/article logo.jpg)
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.
-
/articles/agile-software-visual-studio/en/smallimage/book cover.jpg)
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).
-
/articles/dialogue-sheets-retrospectives/en/smallimage/art icon.jpg)
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.
-
/articles/12-days-agile/en/smallimage/art icon.jpg)
The 12 Days of Agile Christmas
In the spirit of the season we bring you the 12 Days of Christmas in Agile projects.
-
/articles/Succeeding-Dependency-Injection/en/smallimage/article icon.jpg)
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.
-
/articles/feature-injection-success/en/smallimage/art icon.jpg)
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.
-
/articles/kazman-evaluating-software-architectures/en/smallimage/book.jpg)
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.