PM 591 Week 5 Agile Portfolio Management Example

Fund the Teams, Judge the Bets: Agile Portfolio Management for a Studio With Two Live Games, One in Production and Three Prototypes

[Student Name]

University of Phoenix

PM/591: Agile Project Management

Week 5 Assignment

[Instructor Name]

[Date]

Bluebonnet Forge Games, its portfolio, budgets and figures are composites written for a model paper.

Bluebonnet Forge Games, the invented Austin studio in this course, has moved sixteen teams to agile work and built a light program layer to coordinate them. One part of the studio has not changed: how it decides where money goes. Every autumn, the finance director and studio heads build an annual budget that funds each game as a project with a feature list, headcount and cost. When teams learn mid-year that a feature should change or a live game's season needs more content, the budget must be renegotiated. This paper applies agile principles to the studio's portfolio.

The Portfolio Today

The studio's portfolio has six elements: two live games, which earn about 85 percent of current revenue; the new action role-playing game in production, funded partly by a publisher advance; the shared engine; and three small prototypes, a cooperative survival game, a puzzle game for mobile devices and a narrative adventure, each with two or three people, competing to become the studio's next project. Annual budgeting has three problems. It locks in feature lists that teams now revise every sprint. It treats the engine as overhead rather than a product. And it gives prototypes either nothing or a full project budget, with no way to fund a small test and decide based on results.

What Research Says

Stettina and Hörz (2015) studied agile portfolio management in several large organizations and found that practitioners valued transparency of resources and work, frequent portfolio review and alignment of team-level agile with portfolio decisions, while tension remained between agile delivery and traditional budgeting cycles. Kock and Gemünden (2016) surveyed managers responsible for innovation portfolios across many companies and reported that clear strategy, formal portfolio processes and a willingness to terminate projects were linked to better decision quality and agility, with the ability to reallocate resources quickly being part of portfolio agility. Cooper and Sommer (2016) described hybrid models that combine stage-gate investment decisions with agile sprints inside each stage, reporting benefits such as faster response to change and better customer feedback in early adopters. Together these suggest steady funding for known products, quick and evidence-based decisions for new ones and a willingness to stop.

Funding Value Streams

The studio replaces project budgets with four persistent value streams: Live Game A, Live Game B, the new title and the engine. Each receives a quarterly budget sized to its teams, about $1.9 million a quarter for the new title, $1.1 million and $0.8 million for the live games and $0.6 million for the engine. Within that budget, each value stream's leadership decides what to build, guided by its product goals. Budgets are reviewed every quarter against outcomes and may be shifted between streams by up to 15 percent without a full reforecast.

Guardrails

Flexibility comes with guardrails. Each value stream has a spending ceiling for the quarter; any single commitment above $250,000, such as an outsourcing contract, requires portfolio board approval; and every value stream reports spending and outcomes on the same one-page format monthly. Headcount changes go through the portfolio board. The finance director keeps full visibility of actual costs, now organized by value stream rather than by project.

Teams get freedom to decide what to build; the portfolio keeps the power to decide how much to spend.

Funding Prototypes in Small Bets

Prototypes are funded in rounds. Round one: eight weeks and about $90,000 per prototype, ending with a playable build tested by 40 players. Round two, for those that pass: twelve weeks and about $300,000 to build a vertical slice, ending with a larger player test and a market analysis of comparable games. Round three, for at most one prototype: preproduction funding as the studio's next title. At each gate the portfolio board decides to continue, change or stop, based on player test scores, retention in playtests, market data and fit with the studio's strengths. The board expects to stop most prototypes and treats stopping as a success of the process.

Limiting Work in Progress

The board caps active initiatives at the value stream level: no more than three prototypes at once and no new value stream until the new title ships. Within value streams, each may have no more than three major initiatives, such as a new season or a new game mode, in progress at a time. Limits keep scarce people, especially senior engineers and art leads, from being spread thin.

The Portfolio Board and Its Rhythm

The portfolio board, the studio head, finance director, production director and creative directors of each game, meets quarterly for funding decisions and monthly for a short review of outcomes and spending. Its quarterly meeting follows the program-level planning day from Week 4, so funding decisions reflect what teams have just planned.

Outcome Measures

The board uses a small set of measures: for live games, monthly active players, revenue per player and season release reliability; for the new title, playable checkpoints met and player test scores; for the engine, build stability and internal satisfaction; and for prototypes, gate results. Portfolio-wide, it tracks the share of spending going to new products versus live operations, aiming for at least 30 percent on new products.

A Worked Example

In the first quarter under the new model, the cooperative survival prototype scored well in its round one test, with players asking to keep playing; the mobile puzzle game scored poorly on retention. The board funded the survival game's round two, stopped the puzzle game and moved its two people to the narrative prototype, whose test was mixed but promising. Under the old process, none of these choices could have been made before the next autumn budget; this time it took one meeting.

How the Engine Is Treated

Treating the engine as its own value stream changes its standing. Under project budgeting, engine work was charged to whichever game requested it, so improvements that served all three games, such as faster build times, had no sponsor and rarely happened. As a value stream with its own budget and technical product owner, the engine can fund shared improvements directly, and its outcome measures make the value of that work visible to the board. The live games and the new title pay nothing extra for engine work, which removes the temptation to hide engine requests inside feature budgets.

Risks

The model has risks. Value stream budgets may become entitlements that nobody questions; quarterly outcome reviews and the 15 percent reallocation rule counter this. Teams attached to prototypes may resist stopping; the gates use evidence agreed in advance. The publisher may prefer traditional reporting; the new title's value stream reports in both formats until the publisher is comfortable.

Conclusion

Agile portfolio management at Bluebonnet Forge funds four persistent value streams quarterly within guardrails, funds new ideas through small, evidence-gated rounds, limits work in progress and reviews outcomes on a regular rhythm. The approach aligns how the studio decides with how its teams now work, while keeping financial control and the willingness to stop that research associates with better portfolio decisions.

References

Cooper, R. G., & Sommer, A. F. (2016). The Agile-Stage-Gate hybrid model: A promising new approach and a new research opportunity. Journal of Product Innovation Management, 33(5), 513-526. https://doi.org/10.1111/jpim.12314

Kock, A., & Gemünden, H. G. (2016). Antecedents to decision-making quality and agility in innovation portfolio management. Journal of Product Innovation Management, 33(6), 670-686. https://doi.org/10.1111/jpim.12336

Stettina, C. J., & Hörz, J. (2015). Agile portfolio management: An empirical perspective on the practice in use. International Journal of Project Management, 33(1), 140-152. https://doi.org/10.1016/j.ijproman.2014.03.008