<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Management on Panji Gautama</title><link>https://panjigautama.com/categories/management/</link><description>Recent content in Management on Panji Gautama</description><generator>Hugo</generator><language>en</language><copyright>Copyright © Panji Gautama</copyright><lastBuildDate>Tue, 12 Mar 2024 15:08:08 +0000</lastBuildDate><atom:link href="https://panjigautama.com/categories/management/index.xml" rel="self" type="application/rss+xml"/><item><title>Software Estimation</title><link>https://panjigautama.com/software-estimation/</link><pubDate>Tue, 12 Mar 2024 15:07:25 +0000</pubDate><guid>https://panjigautama.com/software-estimation/</guid><description>&lt;p&gt;&lt;img src="https://panjigautama.com/images/0ec368d72828dc9509c66b7600a86ed7-1.gif" alt=""&gt;&lt;/p&gt;
&lt;p&gt;You may be surprised that we are not able to give an estimation as well as we think, and you may be more surprised that not all of the software engineers are able to estimate (properly), most just guesstimate with rough intuition. Though it&amp;rsquo;s not completely wrong, we can actually learn how to estimate properly. If you are graduated from Computer Science major like me, you will remember that software estimation technique is one of the courses by itself.&lt;/p&gt;</description></item><item><title>Thoughts on Developer Productivity</title><link>https://panjigautama.com/thoughts-on-developer-productivity/</link><pubDate>Wed, 15 Nov 2023 07:29:59 +0000</pubDate><guid>https://panjigautama.com/thoughts-on-developer-productivity/</guid><description>&lt;p&gt;&lt;img src="https://miro.medium.com/v2/resize:fit:512/1*nYbbM6V6ZJmlmUToZmLNTw.gif" alt="Color Cycling in Pixel Art | by Stephen Schroeder | Prototypr"&gt;&lt;/p&gt;
&lt;p&gt;I used to have a dream to work at a consulting giant until a few years ago. I worked with a bunch of them, as my parent company decided to hire one of the consulting companies, and they gave me nothing but a mess (Duh! 🙄). A while back, I stumbled upon this &lt;a href="https://www.mckinsey.com/industries/technology-media-and-telecommunications/our-insights/yes-you-can-measure-software-developer-productivity"&gt;&amp;ldquo;Yes, you can measure software developer productivity&amp;rdquo;&lt;/a&gt; article from the consulting giant, and it sparked debate in a lot of tech blogs/newsletters.&lt;/p&gt;</description></item><item><title>Convergence as Tech Debt Safeguard</title><link>https://panjigautama.com/convergence-as-tech-debt-safeguard/</link><pubDate>Wed, 23 Aug 2023 11:57:15 +0000</pubDate><guid>https://panjigautama.com/convergence-as-tech-debt-safeguard/</guid><description>&lt;p&gt;&lt;img src="https://panjigautama.com/images/9d8fa97f717b9f253324e88c39c99434.gif" alt=""&gt;&lt;/p&gt;
&lt;p&gt;Managing technical debt is never an easy game. Even if we have ideas, we need to compare the impact with the product initiatives/feature that we need to build to ensure we stay strong on the product side and boost the business. So what to do? lo and behold : Diverge-Convergence, comes as one of the strategies.&lt;/p&gt;
&lt;p&gt;&lt;img src="https://panjigautama.com/images/ideas-2.jpg" alt=""&gt;&lt;/p&gt;
&lt;p&gt;Each Sprint diverged into two streams: shaping &amp;amp; building, execute convergence sprint every triples.&lt;/p&gt;</description></item><item><title>Talking about Runbook</title><link>https://panjigautama.com/talking-about-runbook/</link><pubDate>Tue, 24 Jan 2023 21:18:29 +0000</pubDate><guid>https://panjigautama.com/talking-about-runbook/</guid><description>&lt;p&gt;&lt;img src="https://panjigautama.com/images/AchingIncompleteBetafish-size_restricted.gif" alt=""&gt;&lt;/p&gt;
&lt;h3 id="why-do-we-need-a-runbook"&gt;Why do we need a runbook?&lt;/h3&gt;
&lt;p&gt;the alert is only a signal, the very first step; reducing &lt;a href="https://www.splunk.com/en_us/data-insider/what-is-mean-time-to-repair.html"&gt;MTTR&lt;/a&gt; and solving the customer problem is the ultimate goal;&lt;/p&gt;
&lt;p&gt;an actionable alert is one of the repetitive tasks; Adding a runbook for the repetitive task will help to increase debugging, accuracy, and efficiency in the triaging process.&lt;/p&gt;
&lt;h3 id="but-what-exactly-is-runbook"&gt;But.. what exactly is runbook?&lt;/h3&gt;
&lt;p&gt;A &lt;strong&gt;runbook&lt;/strong&gt; is a series of steps and detailed instructions to solve common issues or tasks effectively.&lt;/p&gt;</description></item><item><title>Engineering Metrics</title><link>https://panjigautama.com/engineering-metrics/</link><pubDate>Tue, 06 Sep 2022 09:16:02 +0000</pubDate><guid>https://panjigautama.com/engineering-metrics/</guid><description>&lt;p&gt;&lt;a href="https://www.slideshare.net/panjigautama/metrics-that-matters-in-software-engineering"&gt;https://www.slideshare.net/panjigautama/metrics-that-matters-in-software-engineering&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;bunch of metrics are available to track and give us insights, but are they really that important?&lt;/p&gt;</description></item><item><title>How to work with Panji</title><link>https://panjigautama.com/how-to-work-with-panji/</link><pubDate>Tue, 12 Jul 2022 10:49:23 +0000</pubDate><guid>https://panjigautama.com/how-to-work-with-panji/</guid><description>&lt;p&gt;&lt;img src="https://panjigautama.com/images/SqoS.gif" alt=""&gt;&lt;/p&gt;
&lt;p&gt;A while ago, I wrote this &lt;a href="https://github.com/rhapsodixx/manager-readme"&gt;https://github.com/rhapsodixx/manager-readme&lt;/a&gt;, inspired by the other manager readme. Though it&amp;rsquo;s debatable whether the doc is useful, to me, writing this kind of doc is intended for ourselves - as managers - to force us to think about what kind of managers we want to be and what is our expectation to work with our directs, explicitly.&lt;/p&gt;
&lt;p&gt;3 years afterward, I&amp;rsquo;m rethinking and came up with this&amp;hellip;&lt;/p&gt;</description></item><item><title>Tech Debt Management</title><link>https://panjigautama.com/tech-debt-management/</link><pubDate>Tue, 08 Mar 2022 20:25:54 +0000</pubDate><guid>https://panjigautama.com/tech-debt-management/</guid><description>&lt;p&gt;&lt;a href="https://www.youtube.com/watch?v=n9BUA96ymC0"&gt;https://www.youtube.com/watch?v=n9BUA96ymC0&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;🔗 &lt;a href="https://www.slideshare.net/panjigautama/taming-technical-debt"&gt;https://www.slideshare.net/panjigautama/taming-technical-debt&lt;/a&gt;&lt;/p&gt;</description></item><item><title>Defect/Bug Management</title><link>https://panjigautama.com/defect-bug-management/</link><pubDate>Wed, 17 Nov 2021 08:30:33 +0000</pubDate><guid>https://panjigautama.com/defect-bug-management/</guid><description>&lt;p&gt;&lt;img src="https://panjigautama.com/images/JadedPointlessBufeo-size_restricted.gif" alt=""&gt;&lt;/p&gt;
&lt;p&gt;who doesn&amp;rsquo;t love bugs? they are small yet beautiful&amp;hellip;ly ruining our life 🙂. Bug is inevitable, choosing 0 Bug as your OKR/KPI is an insane choice, it&amp;rsquo;s not impossible but it will astronomically hit your productivity &amp;amp; cost, your best bet is to manage it properly. So how are you organizing and managing these bugs? Assigning the right priority(by assessing its severity) is the key, inspired by a couple of references, here is how I typically categorize them.&lt;/p&gt;</description></item><item><title>Scrum != Agile</title><link>https://panjigautama.com/scrum-agile/</link><pubDate>Thu, 26 Aug 2021 09:54:22 +0000</pubDate><guid>https://panjigautama.com/scrum-agile/</guid><description>&lt;p&gt;On demystifying agile and scrum in software engineering ..&lt;/p&gt;
&lt;p&gt;&lt;a href="https://www.slideshare.net/panjigautama/agile-software-development-compfest-13"&gt;https://www.slideshare.net/panjigautama/agile-software-development-compfest-13&lt;/a&gt;&lt;/p&gt;</description></item><item><title>Software Fragmentation - The Golden Path</title><link>https://panjigautama.com/software-fragmentation-the-golden-path/</link><pubDate>Wed, 25 Aug 2021 09:29:07 +0000</pubDate><guid>https://panjigautama.com/software-fragmentation-the-golden-path/</guid><description>&lt;p&gt;&lt;img src="https://panjigautama.com/images/32f8ee1f68495231452451a2edfe9b7b.gif" alt=""&gt;&lt;/p&gt;
&lt;p&gt;There is a direct correlation between teams that give their engineers autonomy to own their technical decisions and the team&amp;rsquo;s ability to hire and retain A-class or Senior talent. There is a tradeoff, but an acceptable level of chaos in exchange for a stronger sense of individual/team ownership is usually the right one and leads to higher performing teams in the long run - at least this is what I&amp;rsquo;ve been seeing if a couple of companies in Indonesia.&lt;/p&gt;</description></item><item><title>Engineering Growth Framework</title><link>https://panjigautama.com/engineering-growth-framework/</link><pubDate>Wed, 12 May 2021 13:56:50 +0000</pubDate><guid>https://panjigautama.com/engineering-growth-framework/</guid><description>&lt;p&gt;&lt;img src="https://panjigautama.com/images/1c1vsZe.gif" alt=""&gt;&lt;/p&gt;
&lt;p&gt;Growth Framework, Career Guideline, Career Ladder, whatever you call it, is essentially general expectations of each of the grade, sometimes people call it as career ladder, but we at Mekari wanted to take it further down into its philosophy: Framework. In general, a framework is a real or conceptual structure intended to serve as a support or guide for the building of something that expands the structure into something useful.&lt;/p&gt;</description></item><item><title>Manager Manifesto</title><link>https://panjigautama.com/manager-manifesto/</link><pubDate>Fri, 16 Apr 2021 11:41:27 +0000</pubDate><guid>https://panjigautama.com/manager-manifesto/</guid><description>&lt;p&gt;&lt;img src="https://panjigautama.com/images/200w.gif" alt=""&gt;&lt;/p&gt;
&lt;h2 id="manifesto"&gt;Manifesto&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Giving critical feedback or having difficult conversations&lt;/li&gt;
&lt;li&gt;Assessing whether a product is ready for launch&lt;/li&gt;
&lt;li&gt;Designing and executing a realistic roadmap&lt;/li&gt;
&lt;li&gt;Setting good goals with accountability&lt;/li&gt;
&lt;li&gt;Building viable new products&lt;/li&gt;
&lt;li&gt;Managing a team during “war time” versus “peace time”&lt;/li&gt;
&lt;li&gt;Defining quality&lt;/li&gt;
&lt;li&gt;Determining who to hire&lt;/li&gt;
&lt;li&gt;Understanding people’s skills, strengths, and growth trajectories&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="helping-people-reach-a-common-goal"&gt;&lt;strong&gt;Helping people reach a common goal&lt;/strong&gt;&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Listening and learning about people’s aspirations and frustrations.&lt;/li&gt;
&lt;li&gt;Mentoring and advising, generally in the form of providing frameworks rather than here’s-what-you-should-be-doing’s (which is a whole topic for another time).&lt;/li&gt;
&lt;li&gt;Designing better and more efficient ways for people to communicate, work, or learn.&lt;/li&gt;
&lt;li&gt;Context-switching often in your day-to-day.&lt;/li&gt;
&lt;li&gt;Playing a key role in the flow of communication (writing, sharing, meeting, presenting).&lt;/li&gt;
&lt;li&gt;Owning the outcome of the team’s successes and failures, even if you won’t make all the decisions yourself.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;em&gt;note : not mine and nor I wanted to take credit on this points. I took this note awhile ago and unfortunately didn&amp;rsquo;t put the source link.&lt;/em&gt;&lt;/p&gt;</description></item><item><title>Excerpt on Regulated Data : Amount, Duration Data Holding, and Archiving</title><link>https://panjigautama.com/excerpt-on-regulated-data-amount-duration-data-holding-and-archiving/</link><pubDate>Thu, 04 Mar 2021 10:33:06 +0000</pubDate><guid>https://panjigautama.com/excerpt-on-regulated-data-amount-duration-data-holding-and-archiving/</guid><description>&lt;p&gt;Data subjects are entitled to request the ESO delete their PII, and the ESO must do so accordingly. If the data subject does not request such deletion, under MoCI Regulation 20, an ESO shall comply with a five-year minimum statutory retention period or as otherwise required by the relevant supervisory authority. This retention period is calculated from the moment the data subject terminates the use of services of the ESO.&lt;/p&gt;</description></item><item><title>On Establishing Technical Documentation at Mekari</title><link>https://panjigautama.com/on-establishing-technical-documentation-at-mekari/</link><pubDate>Thu, 04 Mar 2021 10:21:42 +0000</pubDate><guid>https://panjigautama.com/on-establishing-technical-documentation-at-mekari/</guid><description>&lt;p&gt;**&lt;br&gt;
**&lt;/p&gt;
&lt;p&gt;&lt;img src="https://panjigautama.com/images/tumblr_mcfqj603fq1rfjowdo1_500.gif" alt=""&gt;&lt;/p&gt;
&lt;p&gt;We all hate time wasters. Documentation often is seen as one of these time wasters, mostly because it is boring to do. Planning is often seen as kind documentation, so there is a natural tendency to just skip this step for efficiency. However, people forget the hidden cost of skipping this documentation step: no agreement on shared understanding may cause the project will take a lot longer than people think, and this is only the beginning of other disadvantages of not having proper documentation.&lt;/p&gt;</description></item><item><title>Engineering North Star Metrics</title><link>https://panjigautama.com/engineering-north-star-metrics/</link><pubDate>Sat, 09 Jan 2021 12:11:10 +0000</pubDate><guid>https://panjigautama.com/engineering-north-star-metrics/</guid><description>&lt;p&gt;In the world where all of the metrics are available to be fetch and tracked, we end up on too many things being measured or worst, too little things that are being measured. It is impractical to make smart decisions based upon all available data and impossible to make any decision without data, and virtually impossible to make every metric as a priority worthy of improvement. The first challenge is deciding on what to measure, this article is intended to propose following metrics as the de jure metrics that being tracked and constantly improved going forward within tech team that I led so far.&lt;/p&gt;</description></item><item><title>On forming Technical Program Manager team at Mekari</title><link>https://panjigautama.com/on-forming-technical-program-manager-team-at-mekari/</link><pubDate>Sun, 03 Jan 2021 17:12:39 +0000</pubDate><guid>https://panjigautama.com/on-forming-technical-program-manager-team-at-mekari/</guid><description>&lt;p&gt;&lt;img src="https://panjigautama.com/images/0_v_qNjzpzTWJsFCtW.jpg" alt=""&gt;&lt;a href="https://medium.com/swlh/product-manager-vs-project-manager-vs-technical-program-manager-e45d0cf32e01"&gt;credit &lt;/a&gt;&lt;/p&gt;
&lt;p&gt;As the company growing and more product verticals are coming in, and more competitors coming in not only from Indonesia but also big players from outside the country, there are needs from stakeholders and management (C/VP levels) to ensure we are delivering our initiatives more than ever. Hence, ensuring a team to be self-organized, transparent, and great visibility of ongoing and upcoming project progress are very critical. Spotting potential delays early and doing continuous improvement on how we structure the team and do communication within the team is also essential for us to achieve effective &amp;amp; efficient productivity.&lt;/p&gt;</description></item><item><title>Answering Yes/No Question</title><link>https://panjigautama.com/answering-yes-no-question/</link><pubDate>Sun, 03 Jan 2021 16:41:04 +0000</pubDate><guid>https://panjigautama.com/answering-yes-no-question/</guid><description>&lt;blockquote&gt;
&lt;p&gt;Your boss answering a simple yes or no question: &lt;a href="https://t.co/8uTFWpNyTV"&gt;pic.twitter.com/8uTFWpNyTV&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;&amp;ndash; shelby wolstein (@ShelbyWolstein) &lt;a href="https://twitter.com/ShelbyWolstein/status/1258803845012086784?ref_src=twsrc%5Etfw"&gt;May 8, 2020&lt;/a&gt;&lt;/p&gt;
&lt;/blockquote&gt;</description></item><item><title>Different types of 1:1 conversations visualised</title><link>https://panjigautama.com/different-types-of-11-conversations-visualised/</link><pubDate>Sat, 02 Jan 2021 13:50:43 +0000</pubDate><guid>https://panjigautama.com/different-types-of-11-conversations-visualised/</guid><description>&lt;p&gt;&lt;a href="https://twitter.com/thisisneer/status/1264537589031165952"&gt;Original Thread&lt;/a&gt;&lt;/p&gt;
&lt;h4 id="1-ping-pong"&gt;#1. Ping Pong&lt;/h4&gt;
&lt;p&gt;Both parties are equally engaged and curious about the other. Answers are thoughtful, and each participant always turns their answer back into a question for the other.&lt;/p&gt;
&lt;p&gt;&lt;img src="https://panjigautama.com/images/conversation-1.png" alt=""&gt;&lt;/p&gt;
&lt;h4 id="2-interview"&gt;#2. Interview&lt;/h4&gt;
&lt;p&gt;One person takes the role of questioner, the other person takes the role of answerer. Conversations like these can have two implications:&lt;br&gt;
i) imbalance in interest in the other&lt;br&gt;
ii) perceived hierarchy or power dynamics&lt;/p&gt;</description></item><item><title>Tech Resume</title><link>https://panjigautama.com/tech-resume/</link><pubDate>Sat, 02 Jan 2021 10:07:21 +0000</pubDate><guid>https://panjigautama.com/tech-resume/</guid><description>&lt;p&gt;Tech Resume is an internal personal profile managed and updated by us as an employee with information including current and past projects, accomplishments in our current company, expertise, impact, motivation, career aspirations.&lt;/p&gt;
&lt;p&gt;The idea itself comes from &lt;a href="https://jvns.ca/blog/brag-documents/"&gt;https://jvns.ca/blog/brag-documents/&lt;/a&gt;, since ourselves don’t remember everything we did in the last 6 months, higher chance that doesn’t remember everything we did. it’s important for our works to be recognized and it also useful for us to see our progression so far as part of our retrospective.&lt;/p&gt;</description></item><item><title>My Ex-Boss Cultural Hints</title><link>https://panjigautama.com/my-ex-boss-cultural-hints/</link><pubDate>Sat, 02 Jan 2021 09:46:38 +0000</pubDate><guid>https://panjigautama.com/my-ex-boss-cultural-hints/</guid><description>&lt;p&gt;&lt;em&gt;⚠️ This isn’t my note nor intent to take any credit.&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;TL;DR: We take our job of building quality services for our customers seriously in every way. Rigor at every level is the only way to do that reliably and efficiently.&lt;/p&gt;
&lt;h4 id="ttt---try-three-things"&gt;&lt;strong&gt;TTT - Try Three Things&lt;/strong&gt;&lt;/h4&gt;
&lt;p&gt;Don&amp;rsquo;t reach out to others unless you have tried a reasonable number of things first. Not only will this stop you from task-switching others, but it will slowly build up your expertise in our tools and procedures. Most of the time, you&amp;rsquo;ll find the answer to your question by the time you&amp;rsquo;ve tried that third thing - without bothering somebody else. This is our equivalent of &amp;ldquo;LMGTFY&amp;rdquo;. Of course, don&amp;rsquo;t go overboard and unproductively go into a black hole of learning everything yourself - that would be the fourth thing and be a waste of time too.&lt;/p&gt;</description></item><item><title>Personal Development — Silent Killers of Productivity</title><link>https://panjigautama.com/personal-development-silent-killers-of-productivity/</link><pubDate>Sat, 02 Jan 2021 09:32:31 +0000</pubDate><guid>https://panjigautama.com/personal-development-silent-killers-of-productivity/</guid><description>&lt;p&gt;&lt;a href="https://medium.com/@rhapsodixx?source=post_page-----1854844dee90--------------------------------"&gt;&lt;/a&gt;Beberapa saat ini saya gemar membaca dan mengikuti beberapa buku dan kursus mengenai personal development. Salah satu kursus yang saya ikuti adalah : &lt;a href="https://www.udemy.com/productivity-and-time-management"&gt;https://www.udemy.com/productivity-and-time-management&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;Semakin kita merasa sibuk, disaat itulah kita harus berhati-hati untuk tidak terjebak pada kesibukan yang bisa mengakibatkan produktivitas menurun.&lt;/p&gt;
&lt;p&gt;Dari kursus tersebut, salah satu topik menarik adalah ada beberapa hal yang tanpa kita sadari mampu menurunkan produktivitas kita secara signifikan. Banyak ‘aha’ moment yang saya dapatkan di kursus ini.&lt;/p&gt;</description></item><item><title>Muhasabah</title><link>https://panjigautama.com/muhasabah/</link><pubDate>Wed, 02 Jan 2019 08:20:00 +0000</pubDate><guid>https://panjigautama.com/muhasabah/</guid><description>&lt;p&gt;So lately I&amp;rsquo;ve been thinking about what should I do better this year and trying to learn from other experienced leaders on how they run their high-performance team. They definitely have some sort of framework/structure on whatever they do, and it&amp;rsquo;s becoming a routine, they do it every day and improve it at the same time - over and over again.&lt;/p&gt;
&lt;p&gt;Then I remember Lara Hogan&amp;rsquo;s blog post on management expectation which brilliant. I realize that to improve ourselves, we need to understand ourselves. I decided to write a manager readme, to get myself know better about myself ( well..its some sort of Panji Gautama&amp;rsquo;s Manual ) - and give a clear and explicit expectation to my team, and here I go: &lt;a href="https://github.com/rhapsodixx/manager-readme"&gt;https://github.com/rhapsodixx/manager-readme&lt;/a&gt;. I found this very useful, and now I&amp;rsquo;m confident about things I should pursue this year.&lt;/p&gt;</description></item></channel></rss>