BT

Facilitating the spread of knowledge and innovation in professional software development

Contribute

Topics

Choose your language

InfoQ Homepage Planning Content on InfoQ

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

  • Adaptable or Predictable? Strive for Both – Be Predictably Adaptable!

    Our efforts to improve software development face the question of what to focus on. Should we govern for predictability without concern of value, maximizing cost-efficiency without concern for end-to-end responsiveness? Or maybe do the opposite and govern for value over predictability, focus on responsiveness over cost efficiency? What we really need is to be predictably adaptable.

  • Q&A with Johanna Rothman and Jutta Eckstein on Cost of Delay

    The book Diving For Hidden Treasures - Uncovering the Cost of Delay in Your Project Portfolio by Johanna Rothman and Jutta Eckstein explores how projects become delayed and provides tools and methods to analyze and limit the costs of delay in projects.

  • User Stories Are Placeholders for Requirements

    It can be difficult to change from a Waterfall approach where ‘business analysts write big requirements up front’ to the Agile practice in which requirements are prepared ‘just in time’, and are the responsibility of the entire team. The secret to success in Agile is ruthless management of scope.

  • Agile Approaches in Test Planning

    At Agile Testing Days 2015, Eddy Bruin and Ray Oei explained how to satisfy the needs of stakeholders who ask for test cases, test plans, and other comprehensive test artifacts without writing large test plans. An interview about test plans in agile, how to make stakeholders aware that they can influence quality, and which agile practices they recommend for testing.

BT