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

  • 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.

  • A collaborative approach for real-world BPM

    Bernd Ruec​ker explores how to achieve a better Business-IT alignment when developing BPM solutions. He describes a methodology which uses BPMN-based process model as center for collaboration where users can discuss and link requirements, business rules or other artifacts, visualize development status, specify business driven test scenarios and much more.

  • Agile Team Meets a Fixed Price Contract

    Fixed price contracts are evil - this is what can often be heard from agilists. On the other hand those contracts are reality which many agile teams have to face. But what if we try to tame it instead of fighting against it? How can a company execute this kind of contract using agile practices to achieve better results with lower risk? This article will try to answer those questions.

  • 5 Configuration Management Best Practices

    There has been a lot of conversation going on around the configuration of applications, and how to manage it. This article explores things people can do from within their code to make their lives, and the lives of anyone else who has to administer or maintain their application, easier. These patterns have been used a number of times on ThoughtWorks projects, and they have proven their worth.

  • Agile Operations in the Enterprise

    We've been hearing about agile operations quite a bit lately. There have been some good talks, articles and a few lively debates. It has even been called the "secret sauce for startups". What about those of us who aren't in a startup or a Web 2.0 company? Is agile operations something that can really work inside a large, established enterprise?

  • Book Excerpt and Interview: jBPM Developer Guide

    A new book by Mauricio "Salaboy" Salatino, the jBPM Developer Guide, provides a detailed jBPM programming guide for Java developers with several real-life examples. InfoQ spoke with Salatino to learn the motivations behind the book and learn from his experience both using and writing about the jBPM Business Process Management suite.

  • Authorizing Process Access and Execution with JBoss jBPM

    Centralized BPM deployments can greatly benefit from the ability to control access to process definitions and instances ensuring that users can use and monitor only a set of processes that they are authorized for. In this article Boris Lublinsky shows how to extend JBoss jBPM to define and support process access authorization.

  • 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.

  • Agile and SOA, Hand in Glove?

    Agile is the hand that works in the glove. SOA is the glove, the scope is enterprise wide. Most principles of SOA and Agile are not in conflict. When they are, they keep each other sane. Agile development without a clear vision of the goals and objectives of the company is futile. SOA without a clear vision how to make it real using agile development principles is a waste of time and money.

  • The Meme Lifecycle

    Julian Everett and Chris Matts describe an IT business case as a meme - one that is competing in the complex ecosystem that constitutes a market sector and show its implications. By taking this view of a business then an organization's short and long term strategies change and we get a completely different view of how and why current development practices exist and persist.

  • mySOA: Agile, Governed and Sustainable

    William El Kaim, Lead Architect at Carlson Wagonlit, provides a rare glimpse at all the choices, and the rationale behind them, he and his colleagues have made while building their organization's Service Oriented Architecture. How does your SOA compare? What will be the major evolutions in the next few years? How will the Cloud impact current SOAs?

  • Agile Teamwork: The Leadership - Self-management Dilemma

    Self-managed teams are unstable and are successful when the ‘Leadership – Self-Management’ dilemma is understood and dealt with. Too much central control destroys agility, inhibits creativity and resists change. Too much self-management leads to chaos and anarchy and destroys a team. A successful Agile Team operates as far along self-management as it can, without tipping over into chaos.

BT