BT

Facilitating the Spread of Knowledge and Innovation in Professional Software Development

Write for InfoQ

Topics

Choose your language

InfoQ Homepage Project Management Content on InfoQ

  • Three Things to NOT Do with Your Software Development Projects

    Experience has shown that a software project that is rushed into development is likely doomed to fail. Estimation and up-front planning are the keys to delivering desired quality without running over schedule or breaking budgets.

  • Q&A on the Book Changing Times: Quality for Humans in a Digital Age

    In the book Changing Times, Rich Rogers explores how technology can help people and describes the role that quality plays in this. He tells a story about how technology affects the life of a journalist, and shows what development teams can do to deliver better products.

  • Q&A on the Book Unscaled

    The book Unscaled by Hemant Taneja explores how startup companies can create capabilities similar or stronger than large companies by unscaling. They compete by renting space and functionality in the cloud, which makes them cheaper and more flexible. They are able to innovate and create better products by using data and exploiting the possibilities that sophisticated AI is increasingly offering.

  • Q&A on the Book Agile Management

    The book Agile Management by Mike Hoogveld explores how the agile principles and values can be implemented in an agile way to improve the flexibility and entrepreneurship within organizations. It shows how the “voice of the customer” should be the starting point for designing the products, services, channels and processes you offer to your customers.

  • PAL (Planned Agile Leadership) Schedule

    Develop a PAL Schedule to harmonize agile methodologies with static package Go Live dates to enable a visual representation of planned project progress, enable the same methodologies used at an agile sprint level to control the project at a high level, act as a harness for quantifiable and measurable high-level deliverables, coordinate project activities and enrich meaningful communication.

  • Scaling Agile – Big Room Planning

    This third article in the series about making scaled agile work explores how to do big room planning. It’s two days of planning together with all program and team members every three months providing an overview of all the work to be done in the next quarter. Towards the end of the two days, team and program objectives for the three months are agreed upon, and risks are discussed and mitigated.

  • Q&A on the Book Fit for Purpose

    The book Fit for Purpose by David Anderson and Alexei Zheglov explores how companies can understand their customers and develop products that fit with the purpose(s) their customers have. It provides a framework to help you understand customers’ purposes, segment your market according to purpose, and manage the portfolio of products and services to create happy customers.

  • Scaling Agile - Master Planning Together

    The first article in the series about making scaled agile work shared a true scaling agile story; the second article described the importance and the how-to’s of slicing your requirements into potential releasable epics. So now we’re ready to build on top of those slices and that common understanding; we’re ready to do the master planning together.

  • Scaling Agile - Slice and Understand Together

    This second article in the series about making scaled agile work digs into how to slice requirements. If this is done right, it will not only result in good slices, but also a common understanding of the product we’re about to build or enhance.

  • Customize Your Agile Approach: Select Your Agile Approach That Fits Your Context

    This is the first in a series of articles that will help you think about how you might want to customize your agile approach for your context. This article explores how to make agile approaches work for you: your work, your team, and your organization. It's about understanding the difference between iteration, flow, and cadence and when you might consider each to customize your agile approach.

  • Scaling Agile – a Real Story

    This is the first in a series of articles about making scaled Agile work with slicing, master planning, and big room planning. It is the true story from one particular program in a financial services company, the EU Mifid regulation of extended responsibility for investment advisors.

  • Transforming from Projects to Products

    Agile Transformation is much harder than most organisations envisage, and can require a major cultural change for the transformation to be effective. Too often we make superficial changes but continue the same behaviour with minor changes to processes to appear agile. But without a change in mindset we fail to see the true impact an Agile Transformation can really have.

BT