BT

Facilitating the Spread of Knowledge and Innovation in Professional Software Development

Write for InfoQ

Topics

Choose your language

InfoQ Homepage Planning Content on InfoQ

  • Scaling Autonomy at Zalando

    Autonomy isn't something you can just give to a team, it’s something that teams learn and earn over time. It has to come with accountability to amplify working towards a purpose. At Zalando, creating the right architecture and organizational structure reduced the amount of alignment needed and freed up the energy to be more thorough where alignment is needed.

  • Q&A on the Book The Professional Product Owner

    The book The Professional Product Owner explains what Product Owners can do to become real entrepreneurs who initiate and drive products, and what teams can do to release frequently. It provides ideas and personal anecdotes for effectively applying the Scrum Product Owner role and activities.

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

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

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

  • Monte Carlo Planning Improves Decision Making

    De la Maza helped a startup IPO by applying Monte Carlo to a planning problem. Learn how Monte Carlo planning provides a rigorous, quantitative account of what the future may bring. It has advantages over standard average case approaches and you can start with a simple Excel spreadsheet.

  • Ultimate Kanban: Scaling Agile without Frameworks at Ultimate Software

    Ultimate Software settled on Kanban as its scaled methodology which went hand-in-hand with the company’s culture of autonomy. Teams define their own process and apply policies specific to their own context. Through the innovative use of flow practices and principles, Ultimate has been able to achieve many of the benefits of a Lean-Agile implementation without the use of a heavyweight framework.

  • Q&A and Book Review on Liftoff, Second Edition

    The book Liftoff, Second Edition by Diana Larsen and Ainsley Nies, provides practices and insights for chartering teams by understanding their needs, building trust, and defining how they will interact in the team and align with other parts of the organization. It's a book for Agile coaches, Scrum masters or agile product and project managers to help teams to understand the why behind the work.

BT