Adaptive Planning Canvas (Part 2)

Adaptive Planning (AP) approach from the Agile software development movement Scrum Framework for Trading

Agile Trading Portfolio Management

I am going to implement Agile methodology in my trading. Agile trading portfolio management applies the principles of agile development to managing a portfolio, division of labor, process design, and project management tools. I don’t have a team, therefore I assume all responsibilities. In big investment firms, Agile Portfolio Management’s investment team assumes the roles of agile teams. Here is a very brief description of the Agile software development team (in brackets Agile portfolio management team) is described:

Roles

  • Product Owner or Product Manager (Portfolio Manager): responsible for the composition and performance of the investment portfolio. Accordingly, they are in charge of assessing the portfolio in light of evolving market conditions, identifying risks or areas for improvement, and setting the research agenda. Portfolio managers are primarily, although not exclusively, responsible for generating new ideas. Typically the trading desk head or a senior trader is responsible for:
    • Defining the product vision and goals
    • Prioritizing the product backlog
    • Ensuring the product meets market needs
  • Scrum Master: Facilitates the Scrum process, ensures the team follows scrum principles, and removes impediments.
    • Scrum Master AKA Research Manager: day-to-day research process, investment checklists, valuation models, and Kanban-style lists, and ensuring the overall quality of the research product.
  • Development Team: (Research Team) Includes traders, analysts, risk managers, and other relevant roles responsible for delivering the product increment.
    • Research Team conducts the front-line investment analysis and is responsible for aggregating and communicating research findings with the entire investment team.

The investment and trading process is organized around the agile concept of weekly sprints to discuss portfolio maintenance, current and new opportunities continually flow through the backlog (watchlist of trading opportunities. My trading day starts with the ‘Scrum’ routine that encourages disciplined, and reflective trading. Reviewing my strategies to minimize losing trades, and working on profit-making strategies is most important. I am flexible to adapt to changes, regular self-evaluation, and consistent performance that professional traders need.

  • an agile process closely resembles the workflow of a well-functioning investment process
  • Agile development is organized around short cycles of work called sprints that can last anywhere from one to four weeks. Sprints are constructed around user stories and designed to address a specific customer pain point.
  • Brief daily meetings, called “scrums”, during the sprint allow the team to share progress, identify obstacles, and prioritize the next steps.
  • Look into your insights to see when your audience is active on Instagram
  • Always be clear on what your CTA is

The capital markets teams collaborate and make decisions in the middle of uncertainty to deliver a ‘financial product’ or a trade or position. The process of developing a software application and the process of managing an investment portfolio are similar conceptually. A portfolio manager and his/her team to analyze the opportunities continuously presented by the markets and make decisions to seek trade opportunities to select asset classes in the portfolio (product) required to delight his end users (investors). In my case, I am both an end user and portfolio manager, a one-man team!

Portfolio: Investment Process Design

It’s important to note Agile methodology here is not about “the trading strategy” for reading , trading the market or devising a trading plan. This is about changing routine.

Jas Mahay

Agile Trading Portfolio Management follows the six steps of an agile process with the weekly sprint to go through the equity, indices, currencies, commodities, and future trade opportunities research process. The portfolio manager (that is me!) determines the research priorities, and one day a week (mostly Sunday evening) the research manager (again me!) studies research work for the next week, and follow-up research on existing positions or potential new investments. The research team(me!) meets briefly each day to discuss time-sensitive issues, share updates on progress, and manage process constraints. At the end of th

  1. Sprint Planning

Design: Sprint Design
The sprint planning: the process of selecting items from the product backlog to work on during the upcoming sprint. A sprint plan is a trade plan

The sprint backlog’s scope is the subset of product backlog items included in the sprint. A sprint backlog is created from a product backlog, so the sprint backlog cannot exist without a product backlog. During each sprint planning meeting, the project manager and their team discuss the priorities of the backlog items with the product manager.

Once the portfolio requirements and research priorities have been set, team review the current idea backlog for new ideas and the weekly quantitative screens to find new ideas to meet the identified portfolio needs. Each week, we select 5-10 new stocks to be included in the sprint. Few, if any, will make it through all of the steps of the research process and be considered for inclusion in the portfolio. This means that over the course of a year 300-500 stocks will pass through our investment process, and we may ultimately invest in just the top few percent of ideas.This planning envolves, agreement on a “prioritised list of tasks” called backlog to complete for the duration of a sprint cycle. Short list potential trade candidates for the coming sprint for current the week. The outcomes the sprint planning:

  • Product Backlog Items (PBIs):
  • Plan: What is product backlog planning?
  • Product backlog planning is about defining the overall vision and goals for the portfilio and creating a prioritized list of features and functionality, while sprint backlog planning is about selecting a set of items from the Product Backlog.
  • The product backlog: a prioritized list of features, enhancements, and bug fixes that the team will work on over the course of the project. When translating to trading Product backlog is Trading objectives, rules, and portfolio, etc.List of potential trade candidates based on my OKR (objectives and key results) also know as “the trading strategy”. For example, for currencies assest class (Forex), I will create a list of potential currency pairs to further analyse, if they worthy of trading for upcomming sprint. May be all or may be none of these potential trade candidates will be traded, but the purpose of sprint planning in advance for my trading process is geared for opening potential positions that meet all requirements, criterial of the analysis. Short listed potential candidates are now part of my Scrum Board.
    • Each PBI is a discrete unit of work that delivers value to the product.
    • They should be clearly defined, detailed, and estimated.
    • Examples of PBIs might include “Implement user login functionality” or “Design a new product feature.”
  • My ‘burndown chart’ for the sprint, my trade in progress, time and goal to show actual vs. planned. I set my trading targets on a quartely weekly basis and measure daily and weekly progress in concrete objective terms.
  • Prioritization:
    • PBIs are ranked based on their business value, dependencies, and technical complexity.
    • The highest-priority items are typically placed at the top of the backlog.
  • Status:
    • The status of each PBI can be indicated using labels or colors.
    • Common statuses include “To Do,” “In Progress,” “Done,” and “Ready for Review.”
  • Acceptance Criteria:
    • Clear and measurable criteria that define when a PBI is considered complete.
    • Acceptance criteria help ensure that the PBI meets the product owner’s expectations.
  • Estimates:
    • The estimated effort or time required to complete each PBI.
    • Estimates can be in relative terms (e.g., story points) or absolute terms (e.g., hours).
  1. Scrum Board

I have a large white board in my room to monitor my portfolio and trades with following columns:

  • To Do – trades you intend to open that day,
  • In Progress (working) – open positions,
  • Done – My closed trades.
  • P and L – The profit and loss of this trade
  • Other info.- relevent info goes here like, upconing events, news and or economic releases that can potntially effect this trade or entire portfolio.

The same information is found in the Scrum board, and primary source of correct and validated information. Scrum board is automated but white board is mannual.

  1. Daily Stand Up

Before the market open, the bigger trading firms have meetings ‘teams’ to discuss day’s trading agenda, share current situation. I am a individual trader, so I watch my white board and scrum board to see opened positions, any red flags, changing conditions and other things on my trading mind. Than I complete my morning market analysis for the potential trading opportunities.

Teams use these to share what tasks each member completed the previous day, what they’re working on today and any impediments. Although Scrum dictates that these are team meetings I happily stand up in front of my board and have this discussion aloud, reassuring myself this isn’t the first sign of madness. This is best conducted after you’ve done your morning market analysis as this is probably when you’ve decide what trades you will make that day. This is a daily opportunity to review progress to goal and adjust your daily targets where necessary.

Understanding the blockers to achieving the day’s target is an important part of being holistically aware of your trading. These blockers may be external in the form of market uncertainties, big announcements, and unclear technical analysis or they may be internal: your schedule today might not allow you to make as many trades as you need or maybe you’re not feeling ‘in the zone’. Impediments can be a symptom of looming risk so systematically increasing your awareness of potential blockers better equips you to respond and adapt before problems occur.

What determines the priority of items in a sprint backlog?

  • Team capacity (Buying Power) and sprint goals (trading goals) determine the priority of items in a sprint backlog. The product owner owns the product backlog. The development team owns and maintains the sprint backlog. The product backlog forms part of a product’s long-term strategic plan and evolves with the product.
  • Just because this is called a Daily Stand Up, don’t be fooled into thinking that this only works for day traders – all the tools discussed here work on most timescales. For example, if you’re a swing trader leaving trades open for various periods, the cards on your Scrum Board remain ‘In Progress’ for longer. This doesn’t detract from the usefulness of Scrum, which forces you to constantly evaluate your trades and strategy to make sure you’re always on top of your game.
  • Develop: Thesis Development (Level 1 Research)
    • The first phase of the fundamental research process involves evaluating the stock’s fit across the four metrics that we most highly value – Fundamentals, Management Quality, Valuation, and Catalyst – to develop an investment thesis that will later be tested.
    • During Level 1 Research, the investment team spends 30 minutes to an hour researching each company in the weekly sprint with the objective of finding a reason to disqualify it from further consideration. We may decide to stop doing work on an investment during this qualification phase for any number of reasons, including excessive leverage, unattractive valuation, unremarkable fundamentals, concerns regarding management quality or corporate governance, insider selling, or a company-specific or industry risk with which we are uncomfortable.
    • During Level 1 Research, the investment team adds:
      • Investment Checklist (attached as an Excel file)
      • Revenue breakdown
      • Key value drivers
      • Key research questions
      • Stock recommendation
    • We summarize Level 1 Research for each company in an Investment Checklist that details our findings and whether the idea warrants additional research. At the daily “scrum”, we share our research and work together to identify primary research questions for further study with the goal of better understanding the company’s three or four key value drivers.
  • Test: Thesis Testing (Level 2 Research)
    • The second phase of the research process involves testing the thesis developed during Level 1 Research through a thorough analysis of the fundamental drivers of the company that incorporates both primary and secondary research.
    • Level 2 Research involves reviewing company filings, transcripts, and investor presentations. We also speak with sell-side analysts, industry experts, other investors, and members of the company’s management team. Finally, we look for alternative sources of information to complement our research process.
    • During Level 2 Research, the investment team adds:
      • Primary and secondary research notes
      • Financial model (attached as an Excel file)
      • Investment Thesis
      • Updated stock recommendation
      • Stock strategy
    • Finally, once a company is included in the portfolio, the Trello card serves to memorialize the investment team’s ongoing maintenance research and quarterly updates.
    • We summarize Level 2 Research for each company with an Investment Thesis and a Financial Model, as well as updating the Investment Checklist we created during Level 1 Research.
  • Release: Investment Decision
    • When we have compiled enough information on a Level 2 Research candidate – sometimes in a matter of hours, sometimes in a matter of weeks – we proceed to the Investment Decision phase.
    • Investment decisions are taken after each team member has had a chance to review the research – and ideally after taking a walk or catching some fresh air to put ourselves in the right frame of mind to make a decision.
    • In the Investment Decision phase we decide between three options:
    • Investment Decision
      • Place the company on a watch list with a price limit or a time limit
      • Return the company to the Idea Backlog for consideration at a later date, even if we ultimately pass opportunity.

In short, daily stand up is first thing to do to begin my trading day, review progress to goal, trade management, and plan adjustmnets if and when seem necessary

  1. Sprint Review
  • In software, sprint review is usually a demo of MVP (minimum viable product) and review of the software. But for me (a trader), my product is a trade, points, pips and positions. This weekly review on Friday, is done after market close or my trading day is concluded.
  • At the end of each sprint, the team assesses the sprint’s success in delivering against our objectives and looks for ways to improve the process. In a dynamic environment like the financial markets, no one sprint is identical – but therein lies the strength of an agile method. The objective is to be at once flexible and collaborative with respect to the product and specific and exacting with respect to the process.
  • Investment Process Tools
    In conjunction with our Agile Equity Portfolio Management method, we have built a series of tools used throughout our investment process. These models incorporate both internally generated and third-party data. Many of the tools referenced above – the quantitative screens, the Investment Checklist, and the Financial Model – are proprietary to our research process and designed to fit our particular investment style.
  • However, there are project management tools that are broadly available to all investment teams or even individual investors who are interested in employing the Agile Equity Portfolio Management method. While there are many products to choose from, we made our lives easy by opting to go with the market leader – Trello.

This is my physical board located near my trading station. My ‘dashboard on table has 4 columns:

  1. To Do – trades you intend to open that day,
  2. In Progress – open positions,
  3. Testing – potential trades you’re testing,
  4. Done – fully executed and closed trades.

The cards from the backlog are pinned in their appropriate location on the board and move them as you progress each trade. Physically engaging with the cards better equips you to critically observe your portfolio, allowing you to spot excessive risk exposure quicker and manage this before you suffer losses.

Trello Boards
We use Trello to manage all aspects of the Agile Equity Portfolio Management process and have created three separate boards – Idea Backlog, Weekly Sprint, and Portfolio – to move companies through the process.

Idea Backlog board

Our Idea Backlog board is the central repository for investment ideas for further research. The companies are categorized by sector and region. Anyone from the team is free to add an idea by creating a new card, adding a brief description of the company, the source of the idea, and why it could be interesting.

Weekly Sprint board

Weekly Sprint board in Trello

The Weekly Sprint board 

The Weekly Sprint board is where the team manages the sprint and advances the companies along through the research process, as previously described. At each juncture, the team decides whether an idea is worth pursuing further, whether it should return to the Idea Backlog, or whether it should be discarded.

Portfolio board

No alt text provided for this image

The Portfolio board is where the team manages the names that are currently in the portfolio. The investment team continues to add to the body of research as new information becomes available and updates a company’s thesis, financial model, and stock strategy at least every quarter.

Trello Cards

Each company has its own Trello card to which the research team adds research and commentary over the lifecycle of the investment – from the time it enters the Idea Backlog to the time it exits the portfolio (and returns to the Idea Backlog).

Company card

At any point in time, each company card is meant to contain the body of research the investment team has compiled, making it a “one-stop-shop” for team members to get up to speed on any existing or potential investment.

When a company is added to the Idea Backlog, the card contains basic company information:

  • Company description
  • Idea source
  • Preliminary thesis

Scrum Board

Portfolio Requirements: A prioritized list of tasks ( I call ‘backlog’) to complete for the duration of a sprint cycle. This is a key opportunity to filter potential trade opportunities for the coming sprint/week. At the end of every week, the portfolio manager meet to review the portfolio, identify risks and opportunities among the current holdings, and discuss research priorities.

I analyse my trades, strategies, objective analyse from the burndown chart, lessons learned and cheching my hypotheses on my strategies. I don want to repeat mistakes, and this is good time to do so.

  1. Retrospective

Hindsight is a 20/20 perfect vision, because we compare agaist the actual, but trading a strategy is not perfect. The weeekly Sprint Review looks at “the trade”, but monthly Retrospective look at the “trading process”.

To evaluate my trading strategy against my trading results, I can measure the process against the trades. Retrospective is an opportunity for me to validate the effectiveness of my strategy and my behaviours over the sprint. Scrum methodology encourages me to ask:

  • What went well?
  • What went wrong?
  • What could I do differently?

The product of Retrospection a list of actions, that I implement to improve my trading strategy. The Scrum routine

A monthly retrospective ensures enough time has elapsed to build up a pattern of data from the burndown charts to make reasonable judgements on efficacy of your trading plan. This is the chance to scrutinise your strategy to ensure it’s up to the task and flexible enough to adapt to the ever-changing market.

As, you can see Agile comes handy into promoting continual improvement, by proactively encourages self-reflection to stop me and my strategy from stagnating.

Concluding Thoughts

Applying the Agile Equity Portfolio Management methodology has brought clear value to our investment process. Among the many benefits, below are a handful that particularly stand out:

  1. Idea generation resides in a single location
  2. Research priorities and status are well defined
  3. Research process is transparent to all members of the team
  4. Research content is dynamic, accessible to all, and can even be shared with potential investors as part of due diligence or ongoing manager evaluation
  5. Documentation provides a record of analysis and decision making and facilitates post-mortem assessments of successful and unsuccessful investments

Leave a Reply

Your email address will not be published. Required fields are marked *