BT

Facilitating the Spread of Knowledge and Innovation in Professional Software Development

Write for InfoQ

Topics

Choose your language

InfoQ Homepage Business/IT Alignment Content on InfoQ

  • Does Your Team Have a Mission Statement?

    Is your team juggling conflicting requests? Is your Product Owner struggling to decide which customer's to serve and which to ignore for now? Does it seem that everyone has a different agenda? Perhaps you need a mission statement

  • Impediments To Your Value-Stream

    Scrum defines an impediment as "anything keeping the team from being more productive" and clearly stresses that teams establish means to remove them as continuously as possible. Joe Little proposes an impediment's scope may be better established as being anything keeping the organization from delivering value.

  • Presentation: Steve Jones on "Driving IT from the Business"

    In a presentation recorded at QCon London, Cap Gemini's Steve Jones explains his concept of a business service architecture. Topics covered include how to apply SOA to existing systems, the problems one runs into when SOA is driven by technology, and the structural and organizational impact of business-driven SOA.

  • IBM's Smart SOA Vision Explained at Impact

    At IBM's Impact event this week, IBM execs re-affirmed the view that the main innovation presented by SOA is business/IT alignment. They presented a business-process centric view of how SOA is an enabler for enterprises to change (agility), as well as their view of Smart SOA, a set of principles / maturity model for SOA based on numerous customer SOA deployments.

  • Avoid JaBoWS as the Basis for your Enterprise SOA

    Nick Malik declares JaBoWS (Just a Bunch of Web Services) are the enemy of Enterprise SOA.

  • New Resources for the Software Architecture

    Several new resources are available for the software architect. Simon Brown and Kevin Seal have made available a set of guidelines for creating software architecture documentation. Mike Kavis also put together a framework to help guide the architect in dealing with the change that new architecture can bring.

  • Understanding Business Value

    Aside from "Agile" itself, "Business Value" may be one of the most widely used buzzwords around the floors of any fresh agile project. But, how many of these projects actually have a good understanding of what they really mean when they're saying it? Joe Little presents his thoughts on this very question.

  • Presentation: Anne Thomas Manes on the Business Value of SOA

    In this presentation, recorded at QCon, Burton Group research director Anne Thomas Manes talks about how to make the business case for SOA. Her talk covers explaining SOA to non-technical business people, various approaches for selling SOA to management and gaining funding for SOA investments.

  • Iterating and Incrementing to 'Get What You Need'

    In "Don't know what I want, but I know how to get it", Jeff Patton described a few ways in which Agile teams and business users miscommunicate, and argued that the agile community needs to be clear about the terms 'iterating', 'incrementing' and 'shippable'.

  • Doer vs. Talker: Working Software over Comprehensive Documentation

    In Are You a Doer or a Talker? Jeff Atwood of Coding Horror echoes the agile manifesto's 'Valuing working software over comprehensive documentation.' Noting an article by John Taber, Atwood draws parallels between transportation studies and transportation construction projects.

  • InfoQ Interview: Hugh Ivory on DSDM's Public "Atern" Release

    DSDM has been called "the grandmother" of the agile methodologies, first released in 1995. Until recently it was only available to members but this year, for the first time, the DSDM Consortium made the "Atern" release available to the public. Director Hugh Ivory provided an overview at Agile2007, including a look at both old and new customer-facing roles in DSDM.

  • Multiple Projects, One Agile Team

    It's not uncommon for an organization to have one group of developers who need to complete multiple projects. In those situations, how should the group be structured, and how should their work be planned and allocated?

  • Is Quality Negotiable?

    If a customer tells you that they are not interested in software quality, that they have a specific scope that must be completed by a specific date - what do you do? Do you listen to the customer and compromise quality? (By the way, what is quality?)

  • Why do Java developers hate BPM?

    John Raynolds asked recently the question: "Why do java developers hate BPM?". His controversial post generated a lot of comments that speak more generally about the growing divide between modeling environments and development environments, and the role of the business in traditional development cycles.

  • Agile Meets Pragmatic Marketing

    Pragmatic Marketing is a product management methodology for the technology industry which seeks to apply values and principles similar to those of agile software development. So what happens when the pragmatic marketers meet the agile developers?

BT