BT

Facilitating the Spread of Knowledge and Innovation in Professional Software Development

Write for InfoQ

Topics

Choose your language

InfoQ Homepage Adopting Agile Content on InfoQ

  • Agile Architecture Interactions

    James Madison shows how architects can bring agile and architecture practices together to pragmatically balance business and architectural priorities while delivering both with agility.

  • Agile at the Office of Personnel Management

    In its attempts to modernize retirement claims processing the Office of Personnel Management had several versions of this project cancelled. The most recent of which used "requirements, design, implement, and test cycles to develop the system. During the testing phases, serious issues became evident". In trying again the director said that they weren't going to repeat the mistakes of the past.

  • Bad Attitudes of Agile

    Christopher Goldsbury explores some "bad attitudes" of Agility - assertions about management, documentation, testing, teams, and schedules that are commonly encountered, but contrary to reality. These bad attitudes find refuge and justification in Agile despite the fact they are false. Addressing these viewpoints before they, potentially, darken a good movement is essential.

  • Confessions of A New Agile Developer

    This short article is a first-person case history of someone taking up Agility for the first time. It covers the problems and reactions that are common to most teams and most developers.

  • Skills for Scrum Agile Teams

    The skills required to be hyper-productive in agile projects are different from those required by a traditional one. This article identifies behavioral and technical skills required for a team to have that edge. Anyone who acquires these "delta" traits should be equipped with the right set of behavioral and technical skills, which enable them to work effectively in an agile project.

  • Manager 2.0: The Role of the Manager in Scrum

    Scrum defines just three roles, Product Owner, Scrum Master, and Team - not Manager. Pete Deemer explores the consequences for Managers, how the managerial role might be redefined (including a sample job description), and appointing the manager as Scrum Master.

  • The Limits of Agile

    The problems faced by teams that are attempting Agile in non-traditional settings aren't that Agile principles are inapplicable, nor that the feedback cycle is doomed to failure; but rather, outside of a certain Agile sweet-spot there are additional barriers and costs to applying Agile techniques. None of these obstacles prevents Agile in itself but each increases the cost of getting to Agile.

  • Who Moved my Product Value?

    At the outset, it seems like agile is all about short-term focus and a product life cycle is typically the polar opposite – it runs the total gamut in the spectrum that is the life of the product, starting from incubation to end-of-life. So, how does one attribute the relationship between the two? This is where product value comes in.

  • How Did the Originators of the Agile Manifesto Turn from Technology Leaders to Leaders of a Cultural Change?

    Based on in-depth interviews with twelve of the seventeen originators of the Agile Manifesto, we describe how technology-driven forces led to the cultural change introduced by the agile approach. This message implies what human aspects and methods, practices and tools should be emphasized in adoption processes of agile software development.

  • Book Excerpt: Succeeding with Agile: Software Development Using Scrum

    This is a book excerpt from Mike Cohn's new book "Succeeding with Agile: Software Development Using Scrum". This article describes the primary adjustments individuals must make as they transition from traditional roles to Scrum. The focus is on how these roles change, rather than on a thorough description of each role.

  • Overcoming Technical Challenges for Adopting Agile Methods in the Enterprise

    This article touches upon challenges to adopting agile methods within the enterprise and provided strategies for addressing them. Set up development environments in a consistent fashion using automated scripts and checklists, facilitate automated testing and continuous integration by using standard tooling and test data transparency, and ensure a stricter criteria for the done definition.

  • Why Agile Adoption Fails in Some Organizations

    How often do you hear that a company attempting to adopt agile practices fails? This article examines and explains the often overlooked organizational reasons that agile fails, why it isn’t obvious, and some potential strategies for coping with organizational impediments. The article’s target audience is managers with budgetary responsibility although technical groups might also find interest.

BT