BT

Facilitating the Spread of Knowledge and Innovation in Professional Software Development

Write for InfoQ

Topics

Choose your language

InfoQ Homepage Business Content on InfoQ

  • Design For Hybrid Agile Adoption

    Offshore Development is a critical success factor for many organizations as is adopting Agile methodologies. However, these two techniques have never worked well together. Overcoming this challenge, “Design for Hybrid Agile Adoption (DH2A)”, is a methodology defined to successfully execute Agile projects in a distributed and out-sourced environment. This article provides an overview of DH2A.

  • Agile Strategy Manifesto

    A successful business strategy starts with unique value creation. But for an organization to realize the full benefit of it’s business strategies it must develop and maintain them using an Agile approach. An Agile mindset and careful application of feedback provided by an iterative implementation will help retain value and turn good business strategies into great business strategies.

  • Extending Oozie

    In this article authors show how leverage Oozie extensibility to implement custom language extensions. This approach can be viewed a specializing workflow language for a given company/line of business.

  • Oozie by Example

    End to end Oozie example, including process design, resource coordinator and workflow implementation

  • Introduction to Oozie

    Basic introduction to Oozie - a framework allowing to combine multiple Map/Reduce jobs into a logical unit of work.

  • Interview and Book Excerpt: CERT Resilience Management Model

    CERT Resilience Management Model (CERT-RMM), developed at Software Engineering Institute (SEI), defines the processes for managing operational resilience in complex risk-evolving environments. InfoQ spoke with Rich Caralli, Technical Manager of the CERT Resilient Enterprise Management Team, about RMM framework and the book he co-authored.

  • Interview: William E. Perry - Author iTeams – Putting the “I” Back Into Team

    In his book, iTeams – Putting the “I” Back Into Team, author William E. Perry demolishes the cliché - "There is no ‘I’ in team." As Perry explains, the phrase is nonsense because it is the individual differences in team members that make teams great. In this interview, Ben Linders explores with the author the motivations for writing the book as well as some of the key thoughts.

  • Are You a Whole Team?

    Key to the success of Agile is a "Whole Team", a cross functional team of generalizing specialists. A group that works across boundaries. Matthew Philip diagnoses some of their common problems, such as "Emphasis on Titles", the "Hero Culture" and more. Matthew looks at the root causes and possible cures.

  • The Curse of the Change Control Mechanism

    Unprecedented levels of change caused by the pace of innovation are stretching traditional contract models to the breaking point. As more organizations adopt Agile and Lean for the development of innovative/complex products and services, new contract models are needed that accommodate change. The Evolutionary Contract Model, based on Agile / Lean principles, offers promise as a possible solution.

  • A Process for Managing Risks in Distributed Teams

    In this IEEE article, John Stouby Persson and Lars Mathiassen discuss a process for managing risks associated in managing the distributed software projects. The process includes identifying and analyzing distributed-team risks in the areas of task distribution, geographical and cultural distribution, stakeholder relations and communication infrastructure.

  • Brian Chess on Static Code Analysis

    Building security into software applications from the initial phases of development process is critical. Static code analysis gives developers the ability to review their code without actually executing it to uncover potential security vulnerabilities. InfoQ spoke with Brian Chess about static analysis and how it compares with other security assessment techniques like penetration testing.

  • Agile Contracts

    The traditional Waterfall model fits nicely with the way companies buy things: requirements are drawn up, a supplier quotes a price, and everyone signs a legally binding agreement. Contracts written this way seldom offer the freedom to work using an Agile approach. This article examines four separate models available to suppliers and customers for establishing contracts for Agile work.

BT