ScrumSync
Sign in

BacklogChangelog

Changelog

What changed on this project, newest first. The Product Owner keeps this updated: if a story, a point value or the scope looks different from last week, the reason is written here.

October 22, 2026

  • Story 1.13 (Assign Roles) moved from Team 5 to Team 2. The Thursday C5 contract deadline passed unpublished, and Document 35's buffer plan names Team 2 for exactly this scenario. Team 2 now carries 8 Iteration 3 points (was 6).
  • Team 2's step-by-step implementation guides for all their Iteration 3 stories plus 1.13 have been distributed to the team as text guides, with line-by-line commented code and Pest tests. Every team can read the planning documents themselves in the piDSS repository under docs/planning.

October 21, 2026

  • Backlog re-baselined to the Document 32 numbering and the Document 33 v21.5 plan. All 70 existing stories were renumbered to match (the old tracker numbers are superseded: for example old 5.2 Bill estimation is now 5.4, the old 9.x Reference data stories are now 8.x, and the old 6.x Referral stories are now 6.4 and 6.7), 42 missing stories were added with full user-story text, and the 110 planned points are allocated across Iteration 3 (59) and Iteration 4 (51) per the team plan.
  • Removed from scope at the Product Owner's direction: the what-if sliders (5.19), outage cost (2.7), and the partner invitation stories (3.13/3.14), replaced by normal registration with manager approval (3.6/3.7). Story 8.10 (engines read rates from data) became a Definition of Done rule instead of a story. Direct messaging (6.8 to 6.11) was reviewed and kept; battery necessity (5.3) and the three-scenario comparison (5.18) are protected.
  • Every story is now assigned to the team and iteration that will build it, per the Iteration 3 and 4 allocation in the team plan.
  • Every story now shows its dependencies: what it needs finished first, and what is waiting on it, including cross-team contract notes (C1 to C5). They appear on team pages, on board cards, and inside the story detail view.
  • Team pages rebuilt: the team's stories now sit at the top of the page where they are easiest to see, and every story is clickable to open the full detail (user story, shall statements, simplified notes, dependencies and activity).
  • New User journeys guide page: how a visitor, client, technician, installer, supplier and the platform team each use piDSS end to end.
  • Product Goal and the shared Definition of Done updated to the 21 October plan: manual test tables remain mandatory, automated test files are permitted alongside them.

September 23, 2026

  • Production information removed from the product. A teammate asked how we would measure what a system produces: without monitoring hardware we can only guess, and a guess is not worth showing.
  • Upgrades stay simple: the site shows what your budget buys today next to the cost of the full system. No staged plans, because a budget now is not a promise about next month.
  • Backlog rebuilt around how the team learns. Stories are now pages and lists (the stuff teams can build right now); every add, edit and remove is its own separate story; and the calculation engines wait in the backlog, written without specific numbers or methods, until the class covers that material.
  • Sir's list is in: new list modules for clients, suppliers, installers, technicians, subscription packages, maintenance plans, products and services, plus a My system page where customers record solar equipment they already own.
  • Every story now has a Simplified tab: plain words explaining exactly what to build, so nobody has to guess what a story means.
  • Stories can be moved back a stage without releasing them (team and sprint stay attached).
  • Upgrades now ask for three things: what you already own, the space you have available, and your budget. The recommendation fits all three.
  • The product page was rewritten to explain the finished product: by I4 this is a working solar business platform, and the current lists are phase one of it.

September 22, 2026

  • Direction locked in by the Product Owner: the product is the calculator core, plus a supplier directory with referral requests, referral tracking and simulated commissions and listing fees, plus loans and a staged growth plan. The loans and growth plan come straight from the original project brief.
  • Backlog review: 25 stories, 55 points. Easier stories were re-pointed down (register and log in is now 1 point, since the class had most of it built already). Real engine work keeps its weight at 3 to 5 points.
  • Stories no longer carry a sprint. A story gets assigned to an iteration only when a team pulls it, the way sprint planning is supposed to work.
  • Wording across all stories: “electrical equipment” instead of “appliances”, because the product serves businesses and that is the language of the project brief. Stories are also technology neutral now: no “page” or “click” wording, so they can be built for any interface.
  • Sprint goal saving on team pages: clearer guidance about who can save, and regression tests now cover saving a goal and editing an existing one.
  • New guide pages for the team: the product direction in plain words, the calculations explained, and the break-proofing list.
  • Coverage audit: the whole backlog was checked against the product direction, independently and twice. Three promises had no story behind them, so three stories were added: 1.2 Property profile (sizing that respects your actual roof), 6.2 Bill comparison (before and after solar, side by side) and 9.3 Results with assumptions (every number shows the assumptions behind it). The backlog is now 28 stories, 61 points.

September 21, 2026

  • Team pages: member sub-roles added. A Scrum Master can set each member's working role: Developer, Business Analyst, Designer, Implementer or Tester. These are the roles that rotate each iteration; Product Owner and Scrum Master stay at the account level.
  • Jabar added to Team 3, taking the class to 32 people across 6 teams.

September 20, 2026

  • Project Charter draft circulated to the team: 6 Scrum teams, 32 people, one shared product backlog, completion November 11, 2026.
  • Scope baseline in the charter reflects the team's direction choice at the time (calculator plus catalogue only). Superseded on September 22 when the sponsor asked for wider scope; see the September 22 entry.

September 16 to 17, 2026

  • ScrumSync tracker launched for the class with 7 accounts (1 Product Owner, 6 Scrum Masters), one shared product backlog, sprint goal tracking and a full activity log.
  • Iteration 1 backlog reviewed story by story with the Product Owner and loaded: 15 stories covering the landing pages, accounts, equipment inventory, catalogue and the core calculation engines.