<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Suvajit Gupta on Medium]]></title>
        <description><![CDATA[Stories by Suvajit Gupta on Medium]]></description>
        <link>https://medium.com/@suvajit.gupta?source=rss-6b6acdeb53fc------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*mcFOlmqS7JO5qUK7.</url>
            <title>Stories by Suvajit Gupta on Medium</title>
            <link>https://medium.com/@suvajit.gupta?source=rss-6b6acdeb53fc------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 01:16:14 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@suvajit.gupta/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Dogfooding Appian]]></title>
            <link>https://medium.com/@suvajit.gupta/dogfooding-appian-c0ac2f3e69d2?source=rss-6b6acdeb53fc------2</link>
            <guid isPermaLink="false">https://medium.com/p/c0ac2f3e69d2</guid>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[product-management]]></category>
            <dc:creator><![CDATA[Suvajit Gupta]]></dc:creator>
            <pubDate>Sun, 28 Jul 2019 14:18:10 GMT</pubDate>
            <atom:updated>2020-02-08T17:08:12.829Z</atom:updated>
            <content:encoded><![CDATA[<p><a href="https://www.appian.com/">Appian</a> is a low-code platform that turns your business ideas into enterprise-class applications 20 times faster than via traditional software development. I lead the Appian Engineering team and this article covers why and how we use our software (or “<a href="https://en.wikipedia.org/wiki/Eating_your_own_dog_food">eat our own dog food</a>”) to run and <a href="https://medium.com/appian-engineering/scaling-your-agile-organization-6b8e4aea7447">scale our department</a>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/381/1*wAa3hrPdNJnJ5uIoNnovbw.png" /></figure><p>To make this journey fun, my dog Wally (a connoisseur of dogfood) will be our guide. Let’s start by listing the five reasons we dogfood our features before we ship to paying customers.</p><ol><li><strong>Discovery</strong>: To deliver great usability as shown below, dogfooding helps us experience our platform’s capabilities from different perspectives: as an “Appian developer” building applications to an “Appian user” using them, dogfooding complements our formal usability testing efforts.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*b6UinQiabL__UnjnhCxLDw.png" /><figcaption>Experiencing software from different perspectives (creating it versus consuming it)</figcaption></figure><p>For example, when building a Web Content component to embed external user interfaces within Appian, we made extensive use of dogfooding. We invited people across Appian to leverage an early version of this component for a variety of use cases. They embedded things like Google Maps, which surfaced specific issues that we couldn’t have easily anticipated via our regular software development process. Through dogfooding, we were able to make both the configuration and run-time experience optimal for our customers and the component has been a big hit.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/298/1*s29FSyr469ZuKakwtdFC5w.png" /><figcaption>Enjoying free use of our powerful platform</figcaption></figure><p><strong>2. Leverage</strong>: We strongly benefit from using Appian to run our rapidly expanding department. During my 6 years at Appian, Engineering has grown tenfold. We leverage<strong> </strong>Appian’s low-code platform to build unique applications for our department to power everything from release tracking to <a href="https://medium.com/appian-engineering/traveling-the-software-underground-899865582743">career management</a> and <a href="https://medium.com/appian-engineering/appian-technology-dc3203ecdcb5">technology selection</a>.</p><p>As an example, our team site is shown below and packs all the custom functionality we need to manage our team structure and employee lifecycle.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*9AZqsX1plNFTsCF3ZZLulQ.png" /><figcaption>Our unique needs met by dogfooding our applications</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*rniW2e-A7NEUwSmR820_mg.jpeg" /><figcaption>Walking in customers’ shoes builds empathy</figcaption></figure><p><strong>3. Empathy</strong>: Dogfooding increases our customer empathy because we get a chance to experience the Appian platform just as they do. Our Integration Software Development Kit (SDK) benefited a lot from dogfooding. We didn’t just use it arbitrarily; we built actual extensions that we shipped to the <a href="https://community.appian.com/b/appmarket">Appian App Market</a>. Along the way, we discovered a number of problem areas that gave us paper cuts and eye strain. Dogfooding allowed us to experience these issues as consumers would and surface them more quickly. By the time we released the SDK, we didn’t just have a smoother experience, we had a more powerful and intuitive SDK.</p><p><strong>4. Innovation</strong>: Working with the product also inspires our engineers. Even if dogfooding targets a feature in development, their exposure to other areas of the product has led to a lot of creative side projects that become some of our most beloved product improvements. In the example below, an engineer dogfooding our Process Modeler<strong> </strong>struggled to find things in the palette on the left, so they added a search box. Enhancements like this, which can often languish in the backlog, may get expedited as a result and delight customers.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*aYlc9CzIgJFnVrMoWkr_LQ.png" /><figcaption>The search box above the palette was added by an engineer as a result of dogfooding</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/321/1*XWsxK-bg5hcieZSVOnrfmA.png" /><figcaption>Dogfooding helps us keep a lookout for problems</figcaption></figure><p><strong>5. Quality</strong>: Lastly, dogfooding provides an additional blanket of protection (adding to our comprehensive <a href="https://medium.com/appian-engineering/durable-preventive-actions-how-appian-systematizes-continuous-improvement-fb8676513af2">quality processes</a>) by all employees using our applications to keep a lookout for any regressions. Appian is a complex platform and dogfooding ensures that if we inadvertently break things, we find many of these problems before our customers do.</p><p>For example, we were running a large meeting using an Appian application and people reported strange behavior at times. The application was written a while ago but exhibited intermittent problems when used at this meeting. Digging in, we found a bug that was introduced in a recent internal release and were able to correct it before the next public release.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/269/1*r7DsTnQmP7v_vgY97cvnOA.png" /><figcaption>Paw print with tooltip shows dogfooding plans/status</figcaption></figure><p>Our team gets so much value out of dogfooding, we do it for almost every feature we build. We have an Appian report for our release backlog (below) where each feature gets a color-coded paw print to show its dogfooding status. The tooltip on the paw print shows where and when the feature will be dogfooded. We added a report filter to show features by dogfooding status and follow-up as needed.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*hQuwO__UEPTvw_qT6IZhZQ.png" /><figcaption>Dogfooding tracked via a color-coded paw print icon next to every feature</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/353/1*_EHs-M_kupPAeQnJ2bEO6Q.png" /><figcaption>We make sure teams obey our dogfooding rules</figcaption></figure><p>We have simple rules for dogfooding. Besides a few features that can’t be dogfooded for honorable reasons (for example, because we don’t use SAP at Appian, we can’t dogfood our SAP Connector), everything else must be dogfooded someplace within Appian.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/281/1*FEFZZCuRr5vjMUg-_6EuqA.png" /><figcaption>Product Management leaders are watchdogs for this process</figcaption></figure><p>Our senior Product Management leaders ensure that the entire platform is dogfooded comprehensively. We treat dogfooding like a quality gate to ensure that every feature is delivering the value and satisfaction it’s designed to before it leaves the Appian factory floor.</p><p>When we roll out any new process like dogfooding within Engineering, it can meet some resistance at first. But as we evolve our processes and address peoples’ feedback, we smooth out the rough edges. Months later, we are now using this process fully and effectively.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/273/1*KPLq9lJJrEWgE6qFWl-K5g.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/587/1*ptDOGlc-3Zp_zJLu2V6Ijg.png" /><figcaption>Any new process feels awkward at first… Now we enjoy lots of yummy dog food!</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/432/1*Tjz5n2nxcIk6STaQcFxz5w.png" /><figcaption>Sharing dogfooding experiences is very helpful for our teams</figcaption></figure><p>In addition to the formal dogfooding process outlined above, we also discuss our dogfooding experiences at team retrospectives and Product Management reviews to learn from each other and motivate everyone to partake in this process to build the best low-code platform for our customers.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/286/1*aA5P-X109SVIJ1z2jYjOlQ.png" /><figcaption>Exciting road ahead for dogfooding at Appian</figcaption></figure><p>In the past year, we’ve more than doubled the number of engineers building internal applications with Appian. We hope to do that again this year. Dogfooding is also taking root in other departments — most recently, our Intellectual Property lawyer built an Appian application to manage our patent filing process. Sorry for ending with a lawyer joke…but I hope this article will inspire you to dogfood your product. Woof!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c0ac2f3e69d2" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Traveling the Software Underground]]></title>
            <link>https://medium.com/@suvajit.gupta/traveling-the-software-underground-899865582743?source=rss-6b6acdeb53fc------2</link>
            <guid isPermaLink="false">https://medium.com/p/899865582743</guid>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[careers]]></category>
            <dc:creator><![CDATA[Suvajit Gupta]]></dc:creator>
            <pubDate>Fri, 16 Mar 2018 00:57:13 GMT</pubDate>
            <atom:updated>2023-04-14T00:28:08.322Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/222/0*jwfxJjspaAmg3GKH." /></figure><p>Here is a scrawny student in India with big hair and no life. Barely scraping through his undergrad in Electronics, he should be focusing on his coursework. Instead, he stays up late every night in the computer lab, hacking away at utility applications he can sell to small businesses. He dreams of being freed from the tedium of his coursework to find himself blissfully ensconced in a cubicle — just him, a computer, and code. Fortunately for this kid, his passion is also his salvation. Despite unimpressive grades, his portfolio of utility apps helps get him into to a leading grad school with a new major, where he can finally dig deep into the world of software engineering.</p><p>Yes, I was that kid (sadly, minus the big hair now). Since immigrating to the US in 1989 for graduate studies, not only have I been fortunate enough to realize my dreams, I’ve gone far beyond them. In the intervening years, I’ve traversed a twisted path of roles and titles, and worked for a lot of different companies — three of which went public. What happened to me happens to nearly everyone — the vagaries of life intervened and affected my <a href="https://www.linkedin.com/in/suvajitgupta/">career choices</a>, sometimes serendipitously.</p><p>What I learned in my long and winding journey from entry-level developer, to Executive Vice President of Engineering, has informed how we map out the career options of our engineers here at <a href="https://www.appian.com/">Appian</a> — and it’s very much a map. This map helps employees looking for career direction and their managers tasked with providing that guidance.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*3Gsm11GYHdJFhlVBR-jl1Q.png" /></figure><p>That’s our map for the Engineering career tracks, which progress outward from the bottom left. Each colored line represents a different career track: <strong>Technical</strong>, or <strong>Management</strong>, which you can choose once you get to the transfer station of <em>Senior Engineer</em>. In this article, I’ll explain what each track entails, as well as why it’s designed the way it is.</p><p>As to why it’s styled like an underground transit system, that’s not an accident. Starting off at a new company can be like descending into a subway station in a new city; at some point you find yourself standing on a platform trying to figure out which train to get on. In my career, I’ve held nearly every one of those titles, due to chance or curiosity. I mapped out these tracks based on what I learned, so that every Appian engineer has an opportunity to end up where they want.</p><h3>The Technical Track</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/382/1*x8SWuSvISHZ9ID8Cbwc-hw.png" /></figure><p>Our technical track is for those who really want to focus on hands-on technical work. All fresh-out-of-college hires start on this track. By focusing on your technical prowess, you can work toward becoming an architect, where you can spend your time spearheading transformations, researching new technologies, and playing with cool tools.</p><h4>Stumbling onto the Express</h4><p>When I took my first job as a software engineer, my goal was to become an architect — write great code and become a technical guru by designing and coding complex software. But, I had no real plan on how to get there. I was going to do the only thing I knew how to do — code. I was single, had no social commitments, so I coded all day and many evenings. And, you know what? This was probably the best job I had in my career — I can’t remember being happier.</p><p>Within two years, I shot up to Senior Engineer. I didn’t know if that would lead to becoming an architect someday, since it seemed so far away I wasn’t even thinking about it (and didn’t want to). But, fortune favored me, and I got a bump forward in my career. This time it wasn’t because of my code, but because I met my wife. I wasn’t thinking about my career at all, but after getting married, we decided to move to Washington, D.C. to be closer to our families. With this move came the need to find a new job, and I got hired into a lead engineer role.</p><p>With this new role came new responsibilities that I wasn’t prepared for. Remember, my life was nothing but code up until this point, and now I struggled with focus. How does one write production-grade code while dealing with random interruptions and urgent customer crises? To make matters worse, my boss started including me in discussions about new initiatives and strategies, which tripled my meeting load. I had to quickly improve my time management skills, and while that helped, it was still a challenging overlay of different roles — coder, firefighter, and strategist.</p><p>But it was exactly the experience I needed. With it, I was able to secure a new job as a Technical Lead (the equivalent of a Principal Engineer on our career map). I was living the dream: designing <a href="https://medium.com/appian-engineering/durable-preventive-actions-how-appian-systematizes-continuous-improvement-fb8676513af2">high-quality enterprise software</a>, attending technical conferences, and working with smart engineers.</p><h4>The Technical Train: Knowing How to Get There</h4><p>At Appian, your career options are mapped out. If you want to start out focusing on code, that’s all you have to worry about because you’re already on the right track. While I was fortunate enough to have the necessary skills and opportunities at the right times to advance my career through changing jobs, you don’t have to change jobs to move forward (and you don’t need luck either) on the Appian career tracks. We have formal promotion plans that cover everything you need to work on to secure your promotion (in fact, we built <a href="https://medium.com/appian-engineering/dogfooding-appian-c0ac2f3e69d2">internal applications using Appian</a> for this process). Want to know what skills you need to go from Engineer II to Senior Engineer? It’s all documented, and your manager will setup a plan for you to track your progress toward your goals, and periodically check in with you to review and adjust the plan when necessary.</p><p>To support your progress, we do more than identify what you need to work on, we also provide the training to get you there. Within Engineering, we’ve built an entire <a href="https://medium.com/appian-engineering/appians-engineering-education-creating-a-scalable-and-sustainable-learning-culture-35cef958c0fb">learning organization</a> to grow your technical knowledge and the skills you need to be an effective contributor within the department.</p><p>That’s important because your contributions become more significant as time goes on. With every promotion, you increase your range of influence — something that’s also mapped out. Let’s look at the career map again, but with labels for the expanding spheres of influence:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*AyPM-7m5_t6cBPLnr6HAxA.png" /></figure><p>The labels of “Squad” and “Group” refer to <em>teams</em> and <em>tribes</em> because we leveraged some ideas from the Spotify model (you can read more about it <a href="https://medium.com/appian-engineering/scaling-your-agile-organization-6b8e4aea7447">here</a> if you’re interested). While the actual spheres of influence are more fluid, what you see above illustrates that as you progress on any track, you can affect change over a greater area.</p><h3>The Management Track</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/538/1*bqjMGTg6YnWSvVdjkyMiTg.png" /></figure><p>At the transfer station of <em>Senior Engineer</em>, there’s also the option to get on the management track. While some prefer to avoid managing people, others have a real passion for building great teams and nurturing the talents of others.</p><h4>They Didn’t Teach Me Any of This in School!</h4><p>My experience running teams opened up new kinds of opportunities that I hadn’t considered before, and I ended up getting a new job as a Development Manager. I don’t clearly remember how it happened. I’d always wondered why we needed managers in the first place and couldn’t imagine doing something more boring. One-on-one meetings, interviews, promotions and terminations — why on earth would someone ever want such a job? I guess my boss at the time saw some potential in me and convinced me to give it a try.</p><p>However, the competitive trait that had made me a successful contributor started holding me back as a manager. Contrary to my instincts, I was expected to recognize and promote other people’s ideas and contributions ahead of my own.</p><p>I slowly started to get a handle on the growing number of people and projects I got to work with. I eventually reached a point where I could propose and deliver major programs. While I had only a sliver of time to code, I discovered that spearheading bigger projects and motivating more people to deliver them fascinated me. Instead of designing software myself, I was now designing teams to build great software. As a result of my team’s efforts, the company I worked for went public.</p><p>It was thrilling to not only be a part of this experience, but also be a huge driver of it. It was an experience I wanted to have again, and I wanted to continue on this management track, so I found a new job, this time in senior management.</p><p>This was not as much an escalation of my previous role, but a new kind of role I wasn’t prepared for. Senior management is another step removed from development, and for the first time in a long time, I felt out of control. As a lower-level manager, I could make things happen. I could task people that worked for me. I could roll up my sleeves and jump in when needed. However, as a senior manager, I was managing other managers who didn’t want to be directly told what to do with their teams. I had to learn to influence people through <em>layers</em> of management, and it wasn’t something I was good at. My boss was the CEO, and he told me that though I had a lot of potential, I was falling short.</p><p>Thankfully, rather than demoting me, or worse, letting me go, he elected to pay for an expensive executive coach to help me become a more effective director. Over the next year, my executive coach focused on my weaknesses, like a personal trainer, and taught me about things you don’t learn about in engineering school, like <a href="http://www.danielgoleman.info/topics/emotional-intelligence">emotional intelligence</a>.</p><h4>The Management Train: Empowering People</h4><p>At Appian, the management track is the longest track, and the one that requires the most non-technical education. I was saved by having bosses that believed in me enough to get me the education that I needed to be successful. At Appian, everyone on this track gets that education. We created the Appian MBA, which is a year-long intensive training program that teaches vital humanistic skills and helps new managers grow a strong network of peers to consult with for difficult situations.</p><p>Managers here focus on people and work to make sure they are getting what they need to be successful. They meet regularly for one-on-one meetings and identify growth areas to make recommendations for promotion plans.</p><p>They also strive to get every engineer into the magical intersection of what they like to do (red), what they’re good at (green), and available opportunities (blue). Getting people into this zone is critical for their job satisfaction and maximizes their impact.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/376/1*QVrycGhphwohWDFv3zEAcg.png" /></figure><h3>Going Off Track</h3><p>No matter how you feel today about where you want to go in your career, there may come a time when you want to visit somewhere else just to see what it’s like. For a lot of people, this often means having to leave their job just to explore another option.</p><h4>Train Hopping</h4><p>After fifteen years of being the cost center of the companies I worked for, I started wondering what things looked like on the revenue side. When I occasionally presented our product vision or demonstrated our software, people complimented me on my communication skills and infectious enthusiasm. I wanted to try consulting, where I could interact directly with prospects, customers, and partners. I didn’t have this opportunity at my current job, but a former colleague invited me to join her at her boutique consulting company. I was in a comfortable place where I could try it out, so I accepted the offer.</p><p>I had a lot of confidence going in — after all, I’d met every challenge I’d faced before, and had overcome them in style. I’d developed a wide range of skills and found great success. So, it was no surprise that I hit the ground running with the first project I was placed on: help a big customer bring Agile development to their workforce. No problem. I went in, I assessed the situation, and came up with a storm of amazing recommendations, all of which were enthusiastically received.</p><p>On the second cycle, I returned to the customer and saw that none of them had yet been implemented. I attacked that layer, reinforcing the value of my previous recommendations and identifying a number of process problems that resulted in the lack of follow-through. This volley was not well received, to say the least. Keep in mind, I was used to working at software companies, and driving efficiency and improving process was how I made those places more successful. That was not the same role I needed to play here. The customer said something to the effect of: “While we like Suvajit’s energy, he’s overly aggressive and doesn’t understand how we work. We don’t want him as the primary on this.” And like that, for the first time in my life, I was removed from a project. It felt like getting fired. I was devastated.</p><p>Like all challenges I’d faced before, I was determined to figure this out and get good at it. This time, what I had to learn wasn’t a different way of saying something, but when not to speak. I swore I would master the “two ears and one mouth” (listen more, talk less) consulting mantra. And for the next 6 months I wore a green wristband to remind me to talk less in meetings with customers.</p><p>I bounced back on my next assignment and repaired my confidence by getting good at this consulting thing. But, I also learned along the way that it really wasn’t for me. I yearned to go back to my roots and rejoin a product company. I was utterly fed up with chasing customer budgets and sales targets as a Managing Consultant. The long commute was also wearing me down, as was the frequent traveling. It put a strain on my whole family — we had recently welcomed our second child. Serendipitously, I got a call from a former boss with a new opportunity: Chief Architect at a company called Eloqua with the goal of transforming their decades old platform. I took the job.</p><p>Even though I didn’t stay at the consulting company, it became a functional part of my experience. After the meandering of my professional life, I knew I had acquired the diversity of skills needed to pursue this big bet. I transitioned into the role of a Vice President at Eloqua and built an awesome team that developed award-winning software, which fundamentally powered the company’s IPO.</p><h4>Safe Train Hopping</h4><p>Appian is a big place with many stellar departments and careers to be had. One of the reasons we’ve become so successful is our fundamental belief in retaining the best people. If you reach a point in your career where you wonder if maybe you’d like to try a different career, you’ll find it’s not just OK, it’s welcomed. Appian founders and executives actively support transfers between departments. This allows employees to try different jobs without having to leave the company, which keeps our attrition low. It also helps with cross-pollination of ideas and best practices. There are many people who have moved around within Appian and found a spot that is <a href="https://medium.com/appian-engineering/in-the-wrong-place-at-the-right-place-47bf8458fb5f">perfect for them</a>, without the need to put their career stability at risk by leaving a job just to explore another option. Just within Engineering, we have many people who have moved between Product Management, Software Engineering, and Quality Engineering.</p><h4>The Map Is Not the Territory</h4><p>Even though we make engineers wait until they’ve acquired a good amount of experience before giving them the opportunity to choose a new track, sometimes it isn’t until after a few more stops before they realize they want to go another way. If you decide, after getting to Principal Engineer, that you want to try management, you can!</p><p>However, there is no direct route to Senior Manager from Principal Engineer; you still have to make the transfer at the same place, which means you would work toward being a <strong>Technical Mentor </strong>or<strong> Manager </strong>first and get the appropriate training.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7oMLAUZDiyObm0wHqO-Q5A.png" /></figure><h3>What’s Your Track?</h3><p>Even as a busy Appian executive, I try to stay in touch with my inner technologist. I still code when I can (usually off hours since coding is no longer in my job description) to scratch my technical itch and to retain my efficacy as a software leader. I still personally manage some initiatives from time to time. I work closely with company founders and stakeholders to refine our product strategy. I partner with Engineering managers and leaders to foster a great culture, hire solid engineers, and encourage them to have fun while delivering software.</p><p>My life didn’t unfold as I had imagined, as I zigzagged my way through my career. Some of the best people I worked with have expressed gratitude about being paid to do what they love to do. My parting guidance is to discover where you want to go and go there. Don’t be afraid to hop onto different trains as your interests evolve; we’ve made that exploration safe. It has certainly given me a very fulfilling professional life.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=899865582743" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Scaling Your Agile Organization]]></title>
            <link>https://medium.com/@suvajit.gupta/scaling-your-agile-organization-6b8e4aea7447?source=rss-6b6acdeb53fc------2</link>
            <guid isPermaLink="false">https://medium.com/p/6b8e4aea7447</guid>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[spotify]]></category>
            <category><![CDATA[agile]]></category>
            <dc:creator><![CDATA[Suvajit Gupta]]></dc:creator>
            <pubDate>Wed, 30 Nov 2016 15:09:29 GMT</pubDate>
            <atom:updated>2021-08-12T03:22:33.358Z</atom:updated>
            <content:encoded><![CDATA[<p>If you work in a growing, Agile organization, you will sooner or later face the challenge of trying to keep your multiple, autonomous, Scrum teams rowing in the same direction. I work at Appian where the Engineering team builds a low-code platform for rapidly creating Web/Mobile Enterprise apps. Appian Engineering has grown from a few dozen people to over two hundred over the past few years! Like many software product companies, Appian Engineering has staff with the following core competencies:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*jHCQov7-BTRY2jHaCxSr5g.png" /></figure><p>As we started growing, we quickly realized that we would have to make way more decisions than could be handled in a timely manner by a centralized management team. Additionally, our staff had to be aligned with departmental goals and we had to draw boundaries to clarify ownership of features and bug fixes. We knew we needed to bring some order to the chaos, while still preserving the independence and speed of our teams.</p><p>We came across the <a href="https://dl.dropboxusercontent.com/u/1018963/Articles/SpotifyScaling.pdf">Spotify model</a> that promised both alignment and autonomy by adding Scrum teams called <em>Squads </em>to a <em>Group</em> (Spotify called this a <em>Tribe)</em>, with <em>Chapters </em>and <em>Guilds </em>to connect people across the department that have related skills or common interests.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/624/1*x6Jl8-N51CCMDD92cwvhlg.png" /></figure><p>We have built internal applications to plan and execute our work by <a href="https://medium.com/appian-engineering/dogfooding-appian-c0ac2f3e69d2">dogfooding Appian</a>. We manage our priorities via a <em>Product Annual Plan</em> of initiatives, loosely projected over the next 4–6 quarters. Longer term priorities are maintained in a <em>Product Portfolio Backlog</em>.</p><p>Our investment areas map naturally to Engineering <em>Groups. </em>Each Group owns a multi-year mission. Group-level decisions are made quickly by senior staff such as the Group Development Lead (all Software Engineers report through him/her), the Group Product Lead (all Product Owners report through him/her), and Group Quality Lead (all Quality Engineers report though him/her).</p><p>Each Squad focuses on one of its Group’s missions and takes anywhere from a few quarters to a few years to complete. For example, one of our Squads is working on Mobile Push notifications. As Squads finish their missions, they may re-form around new missions. Squads also allocate up to 20% of their time to maintain code health.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0i9WqaUdXNO7Zhg5n7ykSQ.png" /></figure><p>A few Infrastructure <em>Pods</em> (small teams) work on build and deployment tools. For example, they may help streamline CI (continuous integration) testing to speed up our release <a href="https://medium.com/appian-engineering/rescue-your-mobile-builds-from-madness-using-fastlane-cf123622f2d3">delivery pipeline</a>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/957/0*3lwhN0YxftQ5QAWW." /></figure><p>Chapters are groups of 3–9 people within a Group focused on <a href="https://medium.com/appian-engineering/traveling-the-software-underground-899865582743">professional growth</a>. We set aside 5% of our work hours for “learning time” which may be via Chapters or other less-structured means, ranging from group discussions, spiking, building tools, and getting certifications to consuming or creating training content.</p><p>Guilds form around areas of common interests or needs, such as the Education Guild, which my colleague Dale wrote about <a href="https://medium.com/appian-engineering/appians-engineering-education-creating-a-scalable-and-sustainable-learning-culture-35cef958c0fb#.ulcayx9rm">recently</a>. One fun Guild is our Community Guild, which focuses on ensuring that we retain our sense of community as we grow; they organize team events (picture below) and outings that encourage people to mix and bond, helping keep Appian one of the “<a href="http://www.appian.com/about/news-item/appian-named-2016-top-place-work-washington-post">best places to work</a>.”</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*Z7Y0FtVZLWeniw6N." /><figcaption><em>Community Guild’s Halloween Costume contest winners. The 5 employees on the right are characters from the movie “Inside Out.”</em></figcaption></figure><p>One gap we noticed in the Spotify model was that as we added more teams, we needed a way to keep them aligned along common dimensions of strategy, people, process, and technology. To close this gap, we invented the concept of <em>Councils</em>. Think of a Council as a Guild with mandatory attendance. The Councils below help us manage a rapidly growing department:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/690/1*ofuCV2n0-LLKTp0m-DnMKw.png" /></figure><p>Councils drive cross-departmental improvements and communications. Councils have representation from each Group and departmental function. The diagram below depicts our matrixed leadership model:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/792/1*RHxb8ZO8KiuKXXhbuunTXw.png" /></figure><p>Each Council is led by a Vice President in the department and convenes on a monthly basis. Councils have to be adept at influencing teams and driving organizational change. For example, <a href="https://medium.com/appian-engineering/appian-technology-dc3203ecdcb5">read how</a> we encourage collaboration around the investigation and choice of technologies.</p><p>Council leaders:</p><ul><li>Systematically identify issues and solutions with multiplicative impact</li><li>Exert broad influence, inspire initiative, and spark collaboration</li><li>Organize activities, define processes/artifacts, and measure outcomes</li><li>Relentlessly rally support around strategic initiatives</li><li>Mediate conflict and drive prompt resolution</li></ul><p>We’ve had Councils in Appian Engineering for the last couple of years and continue to refine what they focus on and how they operate. So far, our Councils have played a prominent role in managing departmental strategy/capacity, improving staff management, streamlining our processes, and in formalizing design reviews/debriefings. Could Councils help your organization? We’d love to hear your thoughts!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6b8e4aea7447" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>