<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Team-Management on Daffa Abhipraya</title><link>https://blog.abhipraya.dev/tags/team-management/</link><description>Recent content in Team-Management on Daffa Abhipraya</description><generator>Hugo</generator><language>en-us</language><copyright>© Daffa Abhipraya</copyright><lastBuildDate>Wed, 15 Apr 2026 00:00:00 +0700</lastBuildDate><atom:link href="https://blog.abhipraya.dev/tags/team-management/index.xml" rel="self" type="application/rss+xml"/><item><title>PPL: Code Review at Two Altitudes [Sprint 2, Week 3]</title><link>https://blog.abhipraya.dev/ppl/part-b/s2w3-code-review/</link><pubDate>Wed, 15 Apr 2026 00:00:00 +0700</pubDate><guid>https://blog.abhipraya.dev/ppl/part-b/s2w3-code-review/</guid><description>&lt;h2 id="what-i-worked-on">
 &lt;a class="anchor" href="#what-i-worked-on" data-anchor="what-i-worked-on" aria-hidden="true">#&lt;/a>
 What I Worked On
&lt;/h2>
&lt;p>Two weeks of code review on teammate MRs. Week 1 (2-8 Apr) covered three substantial MRs: hl&amp;rsquo;s CSV import modal (!155), hl&amp;rsquo;s settings management system (!128), and qenthm&amp;rsquo;s ML risk scoring engine (!166) — 44 review points including 7 P0s. Week 2 (9-15 Apr) covered fadhliraihan&amp;rsquo;s AR Staff read-only client access (!171) and fernanda.nadhiftya&amp;rsquo;s communication history UI (!177) — 6 review points including 2 P0s caught through manual testing that static reading missed. Fifty review points total, nine P0s, reviews posted as threaded discussions on every MR.&lt;/p></description></item><item><title>PPL: Team Dev Management [Sprint 2, Week 2]</title><link>https://blog.abhipraya.dev/ppl/part-b/s2w2-code-review/</link><pubDate>Mon, 30 Mar 2026 00:00:00 +0700</pubDate><guid>https://blog.abhipraya.dev/ppl/part-b/s2w2-code-review/</guid><description>&lt;h2 id="what-i-worked-on">
 &lt;a class="anchor" href="#what-i-worked-on" data-anchor="what-i-worked-on" aria-hidden="true">#&lt;/a>
 What I Worked On
&lt;/h2>
&lt;p>Three substantial MRs reviewed this week: Bertrand&amp;rsquo;s cancel invoice feature (SIRA-125), Erdafa&amp;rsquo;s blue/green deployment system (SIRA-134 to SIRA-141), and Rifqi&amp;rsquo;s invoice grouping by status (SIRA-132). Total review points: 29 across P0/P1/P2/P3 severity.&lt;/p>
&lt;hr>
&lt;h2 id="mr-118--cancel-invoice-feature-bertrand">
 &lt;a class="anchor" href="#mr-118--cancel-invoice-feature-bertrand" data-anchor="mr-118--cancel-invoice-feature-bertrand" aria-hidden="true">#&lt;/a>
 MR !118 — Cancel Invoice Feature (Bertrand)
&lt;/h2>
&lt;p>The implementation was solid on the happy path: TDD discipline visible from commit history, clean Router-Service-DB layering, rollback migration included. Review focused on API-level guard gaps that the frontend UI hid but the API did not enforce.&lt;/p></description></item></channel></rss>