InfoQ Homepage Agile Content on InfoQ

Articles

RSS Feed

Newer Older

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
Agile Modeling: Enhancing Communication and Understanding

Modeling supports us in communicating and understanding when we create software solutions. As communication and understanding are two of the most critical aspects of delivering software solutions - modeling is a valuable tool that should not be overlooked. Agile Modeling adheres to and aligns with Agile values and principles and should be one of the practices within your Agile toolkit.

Lee Ackerman
on Nov 21, 2011
Social + Lean = Agile

In today’s increasingly dynamic business environment, organizations must continuously adapt to survive. Change management has become a major bottleneck. Organizations’ need a practical mechanism for managing controlled variance and change in-flight to break the logjam. This paper provides a foundation for applying lean and agile principles to achieve Enterprise Agility through social collaboration

Dave Duggal
on Nov 16, 2011
Virtual Panel: Specification by Example, Executable Specifications, Scenarios and Feature Injection

In the last couple of years terms like Specification by Example, Executable Specifications and Feature Injection have showed up quite frequently in the community, often in relation to Behaviour Driven Development (BDD) or tools like Cucumber or SpecFlow. InfoQ have talked to some of the leading experts in this domain about what these practices are and how they relate to BDD.

Jon Arild Tørresdal
on Nov 10, 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
Agile is at a crossroad: Scale or fail?

Risk management is the hottest topic in IT. Processes for effective risk management and investment decision making will allow Agile techniques to scale beyond projects to the enterprise. Without them, Agile will be confined to the ghetto of development. In this article Chris and Olav present some tools and techniques to identify and manage risks on Agile projects.

Chris Matts Olav Maassen
on Oct 14, 2011
Culture & Methods

Agile Hybridization - Novel Experimentation or "They just don't get it."

Chris Goldsbury discusses the perceived conflict between waterfall and agile processes and identifies a set of context factors that provide guidelines for adopting an appropriate hybrid process between the two.

Christopher Goldsbury
on Oct 05, 2011
The SaaS Development Lifecycle

Many companies today are struggling with how to take advantage of cloud technologies while integrating them into their existing development and operating procedures. This article will show you how to adapt your existing development and operating procedures to the cloud.

Hanu Kommalapati William H. Zack
on Oct 03, 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
Patterns for Continuous Delivery

There is no one-size-fits-all solution to implementing Continuous Delivery. The number and composition of the teams will greatly affect what options are available and what trade-offs need to be made. Staff editor Jonathan Allen reflects on some of the patterns he has observed over the last 15 years.

Jonathan Allen
on Sep 15, 2011

Newer Articles

Older Articles

InfoQ Software Architects' Newsletter

Articles