InfoQ Homepage Agile Techniques Content on InfoQ

Articles

RSS Feed

Newer Older

Managing Security Requirements in Agile Projects

Managing security requirements from early phases of software development is critical. Most security requirements fall under the scope of Non-Functional Requirements (NFRs). In this article, author Rohit Sethi discusses how to map NFRs to feature-driven user stories and also how to make security requirements more visible to the stakeholders.

Rohit Sethi
on Jun 04, 2012
Interview with Simon Baker, Author of No Bull

InfoQ has interviewed Simon Baker, cofounder of Energized Work and the 2009 recipient of the Agile Alliance Gordon Pask Award, author of the "No bull" publication on the past 12 years of Agile.

Marta Jasinska
on May 28, 2012
Swarming Across Distance

"Swarming" is a technique whereby many members of a team work together to deliver a User Story, taking advantage of the skills of many team members working together at the same time. It is recognised as a powerful approach to delivering high quality stories quickly. Johanna addresses how to achieve the same results when your team is geographically distributed?

Johanna Rothman
on May 16, 2012
Net-Map - A Toolkit to Understand and Visualise Stakeholder Influence

Net-Map is a tool developed by Eva Schiffer that allows you through interviews to visualise and analyse how different people and groups influence a particular situation. It is of interest to Agile teams as it can help you understand who your stakeholders are, how they are connected and the level of influence they have. InfoQ recently caught up with Eva and asked her a few questions.

Craig Smith
on May 01, 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
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
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
Interview and Book Review: Specification by Example

Gojko Adzic has written the book Specification by Example, explaining the set of techniques for describing the functional and behavioural aspects of a computer system in a way that they are useful to the development team (expressed ideally as executable tests), understandable by non-technical stakeholders and maintainable to remain relevant despite changing customer demands.

Shane Hastie
on Oct 24, 2011
Test automation and Continuous Delivery

This article shows how automating certain programmable aspects of a test suite can help software delivery. Covered are automated testing, costs per deployment, tests as documentation & manual testing.

Ranjan D Sakalley
on Oct 21, 2011
Organizational Culture and Agile: Does it fit?

Recently, Agile Coach Michael Sahota has been exploring the impacts of organizational culture on Agile transformations. We caught up with Michael and asked him to answer a few questions for our readers.

Todd Charron
on Sep 26, 2011
Active Architecture for Agile Projects

Active Architecture is a type of documentation that helps to bridge the gap between User Stories in Agile Projects and large design deliverables on Traditional projects. It leverages the power and simplicity of User Stories. Unlike traditional design documentation that defines the structure or passive state of the design, Active Architecture defines the actions or active state of the design.

Terry Bunio
on Sep 19, 2011

Newer Articles

Older Articles

InfoQ Software Architects' Newsletter

Articles