<?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[Ataccama SpaceUP - Medium]]></title>
        <description><![CDATA[If you are a scale-up software company struggling to ship a great product to your customers, or you are having problems with the growth and scaling of your product and engineering organization, SpaceUP is here to serve as an inspiration and show how we‘re doing it at Ataccama. - Medium]]></description>
        <link>https://medium.com/ataccama-spaceup?source=rss----20007d403983---4</link>
        <image>
            <url>https://cdn-images-1.medium.com/proxy/1*TGH72Nnw24QL3iV9IOm4VA.png</url>
            <title>Ataccama SpaceUP - Medium</title>
            <link>https://medium.com/ataccama-spaceup?source=rss----20007d403983---4</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 01:05:01 GMT</lastBuildDate>
        <atom:link href="https://medium.com/feed/ataccama-spaceup" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Reinventing Engineering with AI: Can Even a CEO Ship Code Now?]]></title>
            <link>https://medium.com/ataccama-spaceup/reinventing-engineering-with-ai-can-even-a-ceo-ship-code-now-418129ceb880?source=rss----20007d403983---4</link>
            <guid isPermaLink="false">https://medium.com/p/418129ceb880</guid>
            <category><![CDATA[genai]]></category>
            <category><![CDATA[genai-engineering]]></category>
            <category><![CDATA[software-engineering]]></category>
            <dc:creator><![CDATA[Martin Zahumensky]]></dc:creator>
            <pubDate>Mon, 20 Oct 2025 13:58:36 GMT</pubDate>
            <atom:updated>2025-10-20T13:58:32.760Z</atom:updated>
            <content:encoded><![CDATA[<p>Not too long ago, I had a conversation that almost sounded like science fiction. Matt Fisher, an engineering leader from Miovision, told me they’d tested Sourcegraph’s Amp and found that even a CEO could meaningfully contribute to the codebase. It felt like a stretch — so I decided to test it myself.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*iKf7gCw-m0dCvEIgACyBAg.jpeg" /></figure><p>We gathered a few of us on the leadership team — people who hadn’t touched code in over a decade — and ran an engineering offsite. We loaded up a complex enterprise codebase we’d never seen before and set a simple challenge: could we implement real features without prior context (and, in reality, with very rusty coding skills)?</p><p>To my surprise, I managed to get a working dark mode up and running in about 90 minutes. It took a few iterations and feedback loops with the AI agent, but it worked. Meanwhile, one of my VP-level colleagues, who doesn’t actively contribute to the codebase, implemented a set of APIs from our backlog — work that had been sitting on backlog for months — in just a couple of hours. He even sent it for code review.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*rxvitVeO2igYXJ0ZKJzk2g.png" /><figcaption>Dark-mode after 30min, not perfect but decent.</figcaption></figure><p>The result? The code was solid. Not perfect — it reimplemented pagination that already existed elsewhere in the codebase and did it in-memory, so it probably wouldn’t perform well in production. But with a bit more AI-guided iteration, we could’ve had production-ready functionality in a fraction of the usual time. And if we’d properly guided the agent using structured agent.md files, it might’ve done it right the first time.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Y_ZnuOmiuVBiHrc87oHRgg.jpeg" /><figcaption>After midnight, figuring out the Pagerduty clone-app. Cost — 8 USD.</figcaption></figure><p>That day made something very clear: we’re not just talking about augmenting engineers anymore. We’re talking about reinventing the entire engineering workflow.</p><p>Imagine micro-squads of two or three <strong>“super full-stack”</strong> people (I borrowed this term from our Jindřich Regál — and I love it 🙏🏻): part product thinker, part engineer, part designer — using AI to deliver features at ten times the speed. This isn’t theory anymore. It’s happening.</p><p>I’ve been pushing AI adoption hard across our organization and I’m quite fanatic about it — but I wasn’t thinking about it this way. I still believed AI would simply make engineers more efficient. But this is something completely different: from one prompt, you can have a feature — or even a whole application — done. Honestly, if someone had told me 60 days ago this was possible, even I — the AI fan — wouldn’t have believed it.</p><p>But it’s the new reality. Does it have problems? Yes. Will they be solved in the next 60, 90, or 120 days? Absolutely. The future is here now. Adjust — or you won’t exist.</p><h3><strong>From Augmentation to Reinvention</strong></h3><p>Most AI adoption stories today center on augmenting engineers — smarter code completion, better search, Copilot-style helpers that shave off hours of work. But the real shift happening now is far more profound. AI is transforming how we build products, who contributes, and what teams even look like.</p><p>Tools like GitHub Copilot Workspace, Sourcegraph’s Amp, Replit’s Agents, and Anthropic’s Claude aren’t assistants anymore — they’re collaborators. They can take a product idea, write specs, generate tests, build features, and even deploy. Humans guide and review, but the bulk of execution is increasingly automated.</p><p>Sourcegraph’s Amp leads the way: it organizes work into transparent “workstreams,” allowing anyone in the company to see what’s being built and contribute. It makes coding a social, visible act.</p><p>At Anthropic, executives have said that up to 90% of new code is now AI-authored, with engineers acting as editors and integrators — curators of machine creativity.</p><h3><strong>Redefining Roles, Not Just Tools</strong></h3><p>This shift doesn’t eliminate product managers or designers — it blends their roles.</p><ul><li>PMs evolve into builders of outcomes rather than ticket managers. They define problems, prototype with AI, and validate ideas directly.</li><li>Designers use AI to generate variations, test UX flows, and quickly turn ideas into interfaces.</li><li>Engineers focus on architecture, quality, and creative problem-solving instead of boilerplate work.</li><li>Non-engineers can safely contribute to code with automated tests and AI validation layers in place.</li></ul><p>The result: more universal builders who can define, design, and ship without waiting for handoffs.</p><h3><strong>The Rise of Micro-Squads + Agents</strong></h3><p>AI-native companies are moving toward micro-squads — tiny teams with big ownership.</p><ol><li>Tiny, outcome-focused teams. Each 2–4-person unit owns a measurable metric or surface area, supported by AI agents that handle 80–90% of the repetitive execution.</li><li>Company-wide contribution. With modern workflows (Amp, Replit Agents), even marketing, ops, or sales can safely contribute small features or fixes through automated CI and AI-assisted review.</li><li>Transparent, asynchronous collaboration. Public dashboards, workstreams, and leaderboards make work visible, helping people collaborate across functions and time zones.</li><li>AI-native review and integration. Automated testing, linting, and AI code reviewers will be crucial to maintaining quality and speed as the number of contributors grows.</li></ol><h3><strong>Why This Matters</strong></h3><p>In traditional organizations, productivity scales with headcount — until coordination overhead kills it.</p><p>In AI-native orgs, productivity scales with clarity. The clearer the goal, the more autonomously the AI can act.</p><p>This lets companies:</p><ul><li>Ship end-to-end features with drastically fewer engineers</li><li>Increase contribution velocity across the org</li><li>Shorten product cycles from months to days</li><li>Focus human effort on strategy, quality, and judgment</li></ul><p>The key isn’t replacing people — it’s amplifying what small, focused teams can achieve.</p><h3><strong>The New Challenges of Building at AI Speed</strong></h3><p>If AI truly lets us ship 10x faster, the nature of software development will change completely. The bottlenecks that defined the last 30 years of engineering won’t be the same ones holding us back tomorrow.</p><p>We won’t be limited by developer capacity anymore — we’ll be limited by strategic clarity.</p><p>When anyone in the company can build and ship, the challenge won’t be what can we build, but what should we build?</p><p>Today we spend time prioritizing backlogs and choosing from hundreds of potential features. Soon, we’ll face the opposite problem: too much output, not enough focus. Backlogs, grooming sessions, and six-week design sprints may become relics of the past. Why spend six weeks designing the perfect feature when you can ship a working version in two days, learn, and rebuild if needed?</p><p>The classic product workflow — designers drawing, PMs writing specs, engineers implementing — will dissolve. Designers and PMs will commit directly to the codebase. And soon, even sales engineers — or the CRO — might tweak part of the app themselves. That sounds exciting — until three people implement the same feature in three different ways.</p><p>We’ll move from scarcity to abundance of code.</p><p>Instead of reviewing 3,000 lines of code a day, organizations may face 300,000 lines of AI-generated code daily. The real questions will be:</p><ul><li>How do we test this effectively?</li><li>What does QA look like when change is continuous?</li><li>How do we ensure reliability when anyone can contribute?</li></ul><p><strong>We might need to rethink architecture entirely</strong> — designing systems with clear extension points, version control, and guardrails so contributions stay manageable. <strong>Internal development could start to resemble open-source communitie</strong>s, where governance, review, and modularity keep chaos at bay.</p><p>Pipelines, automated tests, and code reviews will evolve radically. AI won’t just write code — it’ll test, benchmark, and review it in real time — creating a self-healing software development cycle where feedback is instant and continuous.</p><p>There’s no precedent for this.</p><p>We’re entering uncharted territory — where the software development lifecycle itself is being rewritten. The only way forward is through rapid learning, experimentation, and embracing the chaos that comes with transformation.</p><h3><strong>A Glimpse of the Future: Reinventing SaaS Itself</strong></h3><p>During that same offsite, we took the experiment further. One of my colleagues used Base44, I used Replit, and we decided to see if we could rebuild something we normally pay a lot for — PagerDuty.</p><p>We pay roughly $60,000 per year for it. It’s a great service, but fundamentally, it allows you to ping people on call and escalate alerts.</p><p>In just three hours, I had a fully functional replacement running:</p><ul><li>I could create employees and assign them to shifts</li><li>I built a list of services, escalation policies, and alert workflows</li><li>I had a dashboard showing average response times by teams and engineers</li><li>I connected it to a service that could call and SMS me directly when an alert fired</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*44zSMGE8DR6jga1J2JIAhw.png" /><figcaption>Glimpse to app UI, fully functional calling my cell-phone and sending SMS alerts.</figcaption></figure><p>It wasn’t a full PagerDuty clone — but it was a working end-to-end alerting system, built in a single afternoon.</p><p>That moment made me realize: the SaaS industry itself is about to be reinvented.</p><p>Simply mind-blowing 🤯.</p><p>And you can imagine how that felt — after 20 years of managing complex engineering teams, I’d built something with my own hands. No need to explain, persuade, iterate endlessly, or compromise. It was under my control. It made me feel like an entrepreneur again — like everything was possible. It was honestly great and incredibly fulfilling.</p><h3><strong>The End of SaaS (as We Know It)?</strong></h3><p>For years, SaaS has been about buy, not build.</p><p>We adopted third-party tools because building in-house was slow, expensive, and required teams of specialists. Plus, you weren’t just buying software — you were buying know-how and accumulated expertise. But AI flips that equation. Now, building small, fit-for-purpose tools might be easier than buying them.</p><p>So, what does this mean for SaaS?</p><p>The next generation of digital-native companies will grow up this way:</p><ul><li>A single founder can build custom internal tools for CRM, onboarding, or reporting using AI.</li><li>Teams will create lightweight, custom-built systems that evolve with their processes.</li><li>The most complex infrastructure or financial systems (ERPs, core banking, etc.) will still make sense to buy.</li></ul><p>Over time, this means hundreds of thousands of micro-tools might be created — so specific and localized that they may never be productized or sold. The boundaries between software companies and software users will blur entirely.</p><p>SaaS won’t disappear — but it will fragment. Maintaining fit-for-purpose tools in-house can still be expensive and distract from mission-critical work, so choosing vendors carefully will remain essential. SaaS companies, to survive, will inevitably evolve their pricing to reflect real complexity and cost.</p><p>Simple, single-function SaaS tools will fade away — replaced by an explosion of company-built, AI-generated microapps.</p><p>As that happens, the software market itself will change. There will be 10x–100x more applications — many ephemeral, built for one company, one use case, one problem.</p><p>The challenge won’t be building software anymore.</p><p>It’ll be discovering and managing it.<strong> How will we make our startups visible in this fog of thousands of apps?</strong></p><h3>✳️ In short:</h3><p>The future of engineering isn’t augmentation — it’s reinvention.</p><p>Tiny squads. Shared ownership. AI as your first teammate.</p><p>And maybe, the end of SaaS as we know it.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=418129ceb880" width="1" height="1" alt=""><hr><p><a href="https://medium.com/ataccama-spaceup/reinventing-engineering-with-ai-can-even-a-ceo-ship-code-now-418129ceb880">Reinventing Engineering with AI: Can Even a CEO Ship Code Now?</a> was originally published in <a href="https://medium.com/ataccama-spaceup">Ataccama SpaceUP</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[SpaceUP: One Year in Orbit]]></title>
            <link>https://medium.com/ataccama-spaceup/spaceup-one-year-in-orbit-377a0b664920?source=rss----20007d403983---4</link>
            <guid isPermaLink="false">https://medium.com/p/377a0b664920</guid>
            <category><![CDATA[organization]]></category>
            <category><![CDATA[spaceup]]></category>
            <category><![CDATA[data]]></category>
            <category><![CDATA[anniversary]]></category>
            <category><![CDATA[software-development]]></category>
            <dc:creator><![CDATA[Natalie Miller]]></dc:creator>
            <pubDate>Tue, 06 Dec 2022 12:40:36 GMT</pubDate>
            <atom:updated>2022-12-06T12:40:36.173Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*gaKrGXb0WYG5dBg3lUn1cg.png" /></figure><p>We’ve officially passed the one year mark on our SpaceUP journey — and what a journey it’s been! Looking back over the last 12 months, it’s hard to sum up everything we’ve gone through in one post. We had our ups and downs, successes and redirections, and learned countless lessons. And we managed to reach the point we’re at thanks to all the support and hard work of all our colleagues.</p><p>Recently our Product and Engineering teams got together to celebrate the first year working under our SpaceUP methodology. When we <a href="https://medium.com/ataccama-spaceup/chapter-7-why-we-needed-to-change-and-how-the-offsite-helped-fec2f56d53f2">met at Lipno last year to plan and officially launch SpaceUP</a>, we knew things would look different one year down the line. But it’s easy to go about our days and miss out on the bigger picture and all the wins, big and small, we’ve had along the way.</p><p>We flew all our Product and Engineering teammates from around the world to Prague for a much deserved SpaceUP celebration and recognition ceremony. Of course we did it in style too, booking Prague’s planetarium for the event, no less. Hundreds of us seated in the planetarium, gazing up at the stars, we took a look back over the last 12 months together. Here are just a few of the proud moments we took a moment to celebrate.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/720/1*6RLeeSnBcFJkZhTsSkum8g.png" /></figure><h4><strong>Version 14</strong></h4><p>One of our biggest and most public accomplishments since the last SpaceUP offsite was revealing Version 14 at the Data People Summit in Boston this October. This new version represents a major shift in how we address customer and market needs, and we’ve already received some positive feedback from customers after the big reveal.</p><p>A few key improvements from the latest upgrade:</p><ul><li>Support of Teams, Federated Governance model through new permissions, collaboration features such as Comments, Data Stewardship, new business workflows and Task Management, as well as Reports catalog / integration with BI tools</li><li>Significantly improved catalog and governance capabilities focus on data activation, as well as data compliance</li><li>New data observability module allows monitoring of whole systems for anomalies in a fully-automated way</li><li>Major integration with Snowflake, including native data processing on Snowflake</li><li>ONE Data — for managing reference data in a user-friendly way</li><li>Ataccama Cloud Portal — the new self-serve way of getting access to Ataccama products</li></ul><p>We are also introducing a new Data Observability module, extending our strong DQ capabilities. And all this, in ONE single platform for Data Analytics &amp; Governance. When we compare this with the Version 13 launch last March, we’re excited for what else is on the horizon for us.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/875/1*KjB_3uFJQwsH2VrlshcbKA.png" /></figure><h4><strong>Status Report</strong></h4><p>Last October we set a handful of clear goals to achieve with the new organization method: end-to-end ownership, empowered teams, speed of delivery, quality of delivery, flexibility and adoption of changes, disruptions and innovations, and celebrating our achievements. To reach these key milestones, we needed to hire 100 new crew members this last year. We grew from a Product and Engineering team of about 160 to roughly 300 members.</p><p>As Ataccama ONE GEN2 continues to grow, we readjusted our internal processes further to cover all our product and engineering needs. We started SpaceUP with seven Spaceports, and created two additional Spaceports to cover our ONE Data and ONE Portal offerings.</p><p>A crucial part of managing the SpaceUP methodology is our feedback process. We’ve had <a href="https://medium.com/ataccama-spaceup/improving-the-methodology-how-we-collect-feedback-to-get-better-d8a552f25380">rounds of surveys sent to all Spaceport members at critical points of our methodology lifecycle</a> to see how we’re actually doing, and if our people are able to achieve what they need to do. We took a look at the survey findings on the planetarium dome, one of the most positive being that 71% of our teammates enjoyed working in the SpaceUP methodology.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/720/1*CiWBVieCMbr5lawmp-QkGQ.png" /></figure><h4><strong>Giving Credit Where Credit is Due</strong></h4><p>Each and every member of our teams played a massive role in our success, and we couldn’t have made these advances this last year without them. After celebrating all we achieved together in 2022, we recognized 20 Ataccamers who went above and beyond to support their Spaceports, and our goals as an organization.</p><p>Managers nominated teammates who they thought best represented those collective goals and the 20 were recognized on stage with applause and thoughtful praise for their individual contributions. Instead of certificates or impersonal gift vouchers, the winners received their very own Star Wars Lego sets. You’d be surprised how happy you can make our teammates with the right gift. :)</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/720/1*BgjEZvlFzHqdn09UCtE82g.png" /></figure><p>After all the presentations were finished and accolades shared, we continued the evening strong with dinner and a party. The photos speak for themselves — we ate, we drank, and we started the second year of SpaceUP with a bang.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/875/1*Rcll0LVS_tebwnmUkIxwtA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/720/1*Sy3O0sHX7ecj5LeHGHqUaw.png" /></figure><p>Want to hop on board and join our SpaceUP journey? See what roles we’re hiring over at <a href="https://jobs.ataccama.com/">jobs.ataccama.com</a>!</p><p>Hope to see you at our next anniversary celebration! 🚀</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=377a0b664920" width="1" height="1" alt=""><hr><p><a href="https://medium.com/ataccama-spaceup/spaceup-one-year-in-orbit-377a0b664920">SpaceUP: One Year in Orbit</a> was originally published in <a href="https://medium.com/ataccama-spaceup">Ataccama SpaceUP</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Timur’s SpaceUP Journey]]></title>
            <link>https://medium.com/ataccama-spaceup/timurs-spaceup-journey-ec15636c5eab?source=rss----20007d403983---4</link>
            <guid isPermaLink="false">https://medium.com/p/ec15636c5eab</guid>
            <category><![CDATA[data-governance]]></category>
            <category><![CDATA[data-quality]]></category>
            <category><![CDATA[data-management]]></category>
            <category><![CDATA[one-portal]]></category>
            <category><![CDATA[spaceup]]></category>
            <dc:creator><![CDATA[Andrej Spasovski]]></dc:creator>
            <pubDate>Fri, 21 Oct 2022 10:18:43 GMT</pubDate>
            <atom:updated>2022-10-21T10:18:43.823Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*cW7nhUWsQPmi8vpBMXxeyQ.png" /></figure><p><strong>Hello Timur! Let’s begin with your journey to Ataccama. How long have you been with us, and how did you get here?</strong></p><p>I’ve been in Ataccama for about a year. I was a subcontractor back in Kazakhstan before coming to the Czech Republic six months ago, and I’ve been here ever since.</p><p>It’s actually a funny story…back in Kazakhstan, I’d already been working for the past three or four years in local companies. And the biggest issue in the Kazakhstan market is that 90% of companies, of tasks, of projects, they’re all B2G — Business to Government. And for many people, including myself, those processes, with a lot of bureaucracy and low-quality products, weren’t the best. I started thinking that I would like to work in an English-speaking team or company, to have a look into how business is going in different parts of the world, especially Europe. I like these destinations. I like the Czech Republic because a lot of students from Kazakhstan come here to study in the universities, so I already had a lot of friends here. When I asked them about the country or the people, most of them said it’s cool. I like it here — it’s proper Europe, but it’s not expensive. :)</p><p>I started looking for companies on LinkedIn. And I basically just found Ataccama. I liked the logo, the colors, the way it looks and thought “Okay, well, why not?” I read a bit about the company, I assumed that it’s a kind of startup but they already had around 200 people working there. So it wasn’t like a startup, it was something bigger than that. I applied and the recruiter contacted me in a few weeks. And after that, I had technical interviews and stuff like this, and at first they rejected me. At the very last interview, they told me you’re good, but we need someone more senior.</p><p>But I stayed in contact with the recruiter. I was literally texting her maybe once a week asking if there were any new opportunities, and she was very kind. So last October, half a year after my first interview, she texted me saying, “Hey, you have an interview tomorrow. Is that okay?” I said sure, why not? The interview was just asking about general things, like, where do you see yourself in five years and stuff like this. We talked for maybe half an hour and the recruiter called me on WhatsApp, because she knew I was really expecting a lot from this interview.</p><p>I was really excited about this opportunity. I thought, Okay, this is probably my chance. She called me after maybe 20 minutes and said “You’re hired!” Then I started preparing the documents. It’s a very long process, it took me almost half a year. And that’s how I got here.</p><p><strong>And how was the beginning compared to what you had been doing before? What were your biggest surprises, where you needed to learn quickly or adjust?</strong></p><p>So I had two first impressions of the company — one when I started to work as a subcontractor, and one when I came here. It was basically all the same. First of all, it wasn’t my first experience with a completely English-speaking team, but it’s a big company, and business is built completely differently here. The first thing that was awesome — those billions of calls and meetings and stuff? They’re actually useful here. Because in my previous company, it was a bit useless. It was just, you know, small talk. And the second thing — people here working in Ataccama, they actually do care about what they do, what the product would be, how it’s going to look.</p><p>Also the onboarding process is very nice because within the first couple of weeks, you’re basically meeting the hub of the company on those meetings. New people go through almost every manager, then they go to their Circle. So maybe for the first two weeks, you might see like 200 people from the company. And for me, it worked very well, because I started to feel comfortable here.</p><p>In my first week in the Czech Republic, I had a very weird feeling at first. Because it was the first time I came to the Czech Republic, and the first time I came to this office. I’d been working with these people for a half a year already. I knew what they looked like, I knew how to speak to them. But still, it was a different film. You come here and you see your team, they see you…I remember, those first days were really weird, because when you see people on Zoom, it’s one thing, but when you see them in natural HD…:) But still, after a few days, I felt really comfortable here because…it’s a simple thing, but people are nice here.</p><p><strong>You joined right after the SpaceUp off-site, so you probably started when they were still setting up the Spaceports, Missions, etc. When you started, was that already going on?</strong></p><p>Yes. But for our team, the ONE Portal team, as I understand everything was super different, because it started with just a small idea. When I was talking with the guys over beer, I understood that ONE Portal wasn’t a big deal from the beginning and there were no plans to make it something very important for the company like it is now. And when I came onboard, the first thing Dominik told me was that we are independent. We are part of the ICOPS Spaceport, but we are as a team — our feature, what we’re doing, we’re completely independent in everything.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/480/1*lvhb6I8wNZ_c1Dzmsg47KQ.png" /></figure><p>We’re a very big team. For the whole first month, I couldn’t understand what we were doing. I had a design, I started to deliver things, but I still didn’t understand what it was supposed to be. As Dominik explained to me, it was supposed to be a super small thing, just a cool thing for the pre-sales team to actually give access to the potential customer to try out that kind of product for a 7- or 14-day trial. That’s it — we’re just connecting with Ataccama products and all we need is to make simple layouts so that people can click on things. And now it’s become much bigger than it was supposed to be, because the top management realized they can use it for much more than just trials. So again, it grew from a team of four people to a team of maybe 40.</p><p><strong>And what do you personally like about the Spaceport setup?</strong></p><p>Well, it was really complicated at the beginning to understand how everything works, because it seems simple at first sight. But when you go into the details, you realize, okay, I don’t quite understand how this should work, how that should work. I think the thing I like most about SpaceUP is the interactivity. When I started to understand things better, I remember thinking, Okay, it’s kind of a game that I have to understand, so I can play it better. Because there are rules, and I just need to learn them. And after that, it became much easier to actually follow the steps and the rules. It feels like its own methodology of how everything works here.</p><p>I wouldn’t say it’s like rebuilding an agile system — it has some comparisons to agile, of course, but it’s different. It’s a bit bigger than agile itself, because it’s not about how the project should be built. It’s about how the whole company is built. I don’t know if other methodologies have the same things.</p><p>For example, I really like the idea of the Ground Crew — if you have a problem, there’s a whole team who is going to react to it ASAP. And it’s very helpful that those people can manage any problem in just minutes or hours. It’s very cool. And this is a small thing too, but the whole of SpaceUP is about those small things, right? These are the ones that I really enjoyed. And I even like the terminology, the words that they use like Mission Landing, All Hands, etc., it really feels interactive. You understand it better and you feel it better.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/480/1*EQzrEoiEwittkcCJaO4ixw.png" /></figure><p><strong>And what about the Mission Observatories?</strong></p><p>I’m not attending every Mission Observatory. But it’s actually a good thing. Every week you have a call when you can actually track what’s going on in the whole company, not only in your team or your Spaceport, but in general. We also have our own engineering observatory. The Circle system is, for me, something completely new. In my previous companies there was something like Circles, but it was probably the most useless thing I’d ever seen, because it was not helpful. It was only about one guy who just read some article about some new cool library or technology going “Hey, guys, this is a cool thing. Check it out.”</p><p>Here, people are really discussing things. And if there is, for example, some major update in technology that we are using, they dedicate a lot of time to actually explain and discuss new features, if we actually need to use new features, if we need to migrate to those new features, or if we can keep it old fashioned. That’s helpful. And that’s the thing that I said before about my first impression: Calls and meetings are actually useful here.</p><p>Want to join Timur and the ONE Portal team? Want to see for yourself how SpaceUP works? Join us!</p><p>Check out our open positions at <a href="https://jobs.ataccama.com/">jobs.ataccama.com </a>and find the best match for you. Can’t wait to hear from you!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ec15636c5eab" width="1" height="1" alt=""><hr><p><a href="https://medium.com/ataccama-spaceup/timurs-spaceup-journey-ec15636c5eab">Timur’s SpaceUP Journey</a> was originally published in <a href="https://medium.com/ataccama-spaceup">Ataccama SpaceUP</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Chapter 7: Why we needed to change — and how the Offsite helped]]></title>
            <link>https://medium.com/ataccama-spaceup/chapter-7-why-we-needed-to-change-and-how-the-offsite-helped-fec2f56d53f2?source=rss----20007d403983---4</link>
            <guid isPermaLink="false">https://medium.com/p/fec2f56d53f2</guid>
            <dc:creator><![CDATA[Tomáš Porazil]]></dc:creator>
            <pubDate>Thu, 30 Jun 2022 13:26:52 GMT</pubDate>
            <atom:updated>2022-06-30T13:29:37.881Z</atom:updated>
            <content:encoded><![CDATA[<h3>Chapter 7: Why we needed to change — and why we went off site for it</h3><p><em>Welcome to chapter 7 of our SpaceUp Series. After covering </em><a href="https://medium.com/ataccama-spaceup/chapter-3-space-up-fundamentals-the-glossary-2a28f8d68e42"><em>Spaceports and Societies</em></a><em>, </em><a href="https://medium.com/ataccama-spaceup/chapter-2-spaceup-or-how-we-changed-the-way-our-product-engineering-works-41e302045b95"><em>Missions</em></a><em>, and </em><a href="https://medium.com/ataccama-spaceup/chapter-4-key-roles-in-the-organization-and-their-responsibilities-62a4d89a52a7"><em>key roles</em></a><em>, as well as going over the </em><a href="https://medium.com/ataccama-spaceup/chapter-6-from-iterations-to-tangible-results-mission-lifecycle-58f0c0e6871"><em>Mission Lifecycle</em></a><em> in our previous chapter, it’s time to answer an important question: Why did we want an offsite in the first place?</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*lGhI-aKgwAedNXzB1Hzryw.jpeg" /></figure><p>We wanted to have an offsite, because we wanted cultural change, to change our mindset. That was the biggest reason. The claim of the whole initiative was “To the moon and beyond,” it was really about this change in mindset. We knew that if we want to have an impact, that it can’t be just another presentation in a hole, because then no one would really feel that something is changing. And we wanted to emphasize this change. That was also the reason behind the SpaceUp name.</p><p>So now we have a claim, and something like a manifesto — since the whole SpaceUp is like a manifesto. It’s codified, we have it written down, you can go back to it, you can read it. And the reason for taking it off site was that we wanted the audience to focus on it, to not be disturbed by anything else. And also, to feel the importance of it. To feel that this is like a checkpoint, like something’s just finished and something new is starting. This is what we wanted to emphasize, that something new is really, really starting.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*a9ai0kxC1IuMZPKMuQH9Sg.jpeg" /></figure><p>Also, when we were discussing the claim of the offsite, we decided that we needed a special visual to go with it. Something that people will remember. So we hired an external artist, and they created a truly special set of visuals. I remember people coming up to me saying that it looks gorgeous, it looks fantastic. Some people even thought it looks too good, which is the aspirational moment I was expecting. I wanted to point out that we’re targeting the next level. We’re not adolescents anymore.</p><p>Another reason is that we suffered after two years of COVID. And we are growing quite fast in product development. One year ago, we had just 100 people and today we have around 215. We doubled the size in just one year. And it was the same at the off site, which happened over six months ago now. But we are still growing at the same pace.</p><p>An example: Michal Klaus, in his introduction at the offsite, asked the audience “Raise your hand if you’ve been in the company for less than six months.” And almost half of the crowd raised their hands. That was interesting, because we really didn’t have a chance to meet each other and create, to launch relationships with each other. So that was also one of the reasons why we really wanted to have this gathering, so people can have an opportunity to build these relationships. That’s important because we are also experiencing a huge cultural change.</p><p>When I joined the company almost three years ago, we had maybe 130–150 people, and now we are at almost 500. Three years ago, almost everything was based on pure human relations. We didn’t have many processes. We just knew who you should come to if you want to get something done. Now, this is changing.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*jssBdYvQ_ajl2biGoIwQrA.jpeg" /></figure><p>Unfortunately, there is a lot more anonymity that comes with the size and we wanted to somehow fight against it. Not just talk to people through screens, but also see them, feel them, see their immediate reactions so that we can adjust our talks and everything else. For us, it was also kind of an experiment. We had tested it with some leaders’ product sites, or technical, or engineering events before the SpaceUP offsite, but we still couldn’t anticipate what the reaction would be. This was also one of the reasons why we wanted to meet in person.</p><p>My strongest memory from the offsite was that I was terrified. I’m not used to talking before such a huge crowd, it was almost 200 people. And I was preparing my talk even while traveling there. But immediately after the first day we started building those relationships — we had an evening program, then we had some team building activities the next day, like minigolf, dragon boats, cycling, etc. So that was the first part…and then maybe the bigger part was that we had separated the crowds to the Spaceports already, because that was a completely new concept. And some of these folks had never even met each other before.</p><p>Before the restructuring, we had around 18 regular-sized Scrum teams of five plus-minus two people, and one of the biggest changes for them was that we put them together into the Spaceports. Some of them were created naturally, but some were made artificially, and they really didn’t know each other. So it was really an opportunity for them to introduce themselves, so they know “Okay, I’m Tomas, I’m a product manager and my passion is juggling,” things like that.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*D9_plbgtmx-wrq70irxHrg.jpeg" /></figure><p>My expectation of the offsite was that each Spaceport will end up with some plan, like “what’s the first objective on which you’re going to focus, how are you going to control the space, what kind of processes will you have there, what kind of people and in which roles will you need there?” But I don’t think all of them were really met at the end of the day, because they spent much of the time on introductions, who they are, and what they want to build. So there were huge discussions, but I think it was really worth it because they needed to find common ground, they needed to find their north star so they knew where they were heading.</p><p>That was really the moment where they could build relationships and bond with their Spaceport. I think they created the basics for their own culture because this is what every Spaceport has now, they have their own culture. Each of them behaves differently because each of the Spaceport leaders has a different personality, with different attitudes towards things. So every Spaceport is different. And that’s totally okay. I think they really created the basics for this on the offsite, because many of the Spaceport leaders weren’t really well-known beforehand.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1n5alrgZFVr9Qxl9AEw28A.jpeg" /></figure><p>At Ataccama you grow really fast, which means you are installing people in key positions when they are not really prepared. Then, you need to provide them with training and mentoring and all the rest. So, you don’t promote leaders, you create leaders. And I think it was also the case for the offsite. With the Spaceport leaders that we installed, including myself, there were people who really weren’t prepared until this point, weren’t known as leaders. So this was also where we needed to introduce them. And I think that’s the whole point with the culture, the relationship-building, and the introductions. You basically let the people grow, giving opportunities to those who — and this is inevitable and will definitely happen — will fail at a certain point. But there’s nothing wrong with that. That’s the buzzword, right? Fail fast. But what I think is really a reflection of Ataccama is that I have never seen anyone blamed for a failure. We are always given a second chance. Or even a third one.</p><p>Enjoyed this article? There’s plenty more where that came from! Check out our previous chapters to follow along on our journey!</p><p><strong>More SpaceUP:</strong></p><ul><li><a href="https://medium.com/ataccama-spaceup/chapter-1-does-it-scale-why-were-rethinking-our-engineering-and-product-organization-93135018aac5"><strong>Chapter 1</strong></a></li><li><a href="https://medium.com/ataccama-spaceup/chapter-2-spaceup-or-how-we-changed-the-way-our-product-engineering-works-41e302045b95"><strong>Chapter 2</strong></a></li><li><a href="https://medium.com/ataccama-spaceup/chapter-3-space-up-fundamentals-the-glossary-2a28f8d68e42"><strong>Chapter 3</strong></a></li><li><a href="https://medium.com/ataccama-spaceup/chapter-4-key-roles-in-the-organization-and-their-responsibilities-62a4d89a52a7"><strong>Chapter 4</strong></a></li><li><a href="https://medium.com/ataccama-spaceup/chapter-5-societies-circles-not-yet-another-product-andengineering-matrix-structure-11fdd1b0bb69"><strong>Chapter 5</strong></a></li><li><a href="https://medium.com/ataccama-spaceup/chapter-6-from-iterations-to-tangible-results-mission-lifecycle-58f0c0e6871"><strong>Chapter 6</strong></a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=fec2f56d53f2" width="1" height="1" alt=""><hr><p><a href="https://medium.com/ataccama-spaceup/chapter-7-why-we-needed-to-change-and-how-the-offsite-helped-fec2f56d53f2">Chapter 7: Why we needed to change — and how the Offsite helped</a> was originally published in <a href="https://medium.com/ataccama-spaceup">Ataccama SpaceUP</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Improving the methodology: How we collect feedback to get better]]></title>
            <link>https://medium.com/ataccama-spaceup/improving-the-methodology-how-we-collect-feedback-to-get-better-d8a552f25380?source=rss----20007d403983---4</link>
            <guid isPermaLink="false">https://medium.com/p/d8a552f25380</guid>
            <category><![CDATA[methodology]]></category>
            <category><![CDATA[feedback]]></category>
            <category><![CDATA[product]]></category>
            <category><![CDATA[data]]></category>
            <dc:creator><![CDATA[Jan Balata]]></dc:creator>
            <pubDate>Wed, 11 May 2022 14:01:31 GMT</pubDate>
            <atom:updated>2022-05-11T14:01:31.358Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4-HSbgzGsfx_Kuu7DBkBZw.png" /></figure><p>In October 2021, we introduced the SpaceUP structure to our team internally (<a href="https://medium.com/ataccama-spaceup/chapter-1-does-it-scale-why-were-rethinking-our-engineering-and-product-organization-93135018aac5">you could read more about how the missions are structured, planned and delivered in our previous articles</a>). There were major changes for the whole Product and Engineering department in the way they work, and also with whom they work. Some teams split, others merged into what we call Spaceports, and some parts of products and features changed ownership.</p><p>We designed the new organizational structure because some aspects of the departments were, to be honest, not working well — there were friction points, lack of feedback, missing ownership, and other issues we knew needed to be addressed to scale and achieve our mission. So, which areas do you tackle first when you recognize you need to change? The major driving factors can be summed up in these key goals:</p><ul><li>improve planning, prioritization and assessment of features</li><li>increase visibility of the work being done in Product and Engineering</li><li>cascade company objectives down into the organization structure</li><li>speed up delivery time and enhance quality; fail faster</li><li>empower teammates to innovate and disrupt</li><li>promote our colleagues’ sense of ownership and responsibility over their work and features, as well as for customers and users</li><li>strengthen knowledge transfer between people and teams</li><li>give proper focus to all parts of the product</li><li>celebrate successes and get feedback on work from customers and users.</li></ul><p>Since then our Product and Engineering team prepared and flew over 30 Missions which took Crews 6 weeks on average to land. The team grew by 60 colleagues in past 6 months as well. The new structure seems to have been adopted well, as shown by the number of Missions and their duration, and as word of mouth spreads on 1:1s upwards within the organization.</p><p>But did we really fix our problems? Does it really work as we intended, and is efficiency as a metric enough? We don’t know. Even before SpaceUP we were capable of delivering new features in a more or less timely manner and we hired new colleagues along the way.</p><h3>SpaceUP as a Mission</h3><p>When we look at SpaceUP through the lens of a Mission lifecycle, there was a long discovery phase at the beginning where the team compared different organization structures and created the first prototypes of the methodology. We iterated with a wider audience and tested if what we proposed made sense. To fly the Mission, we prepared the whole methodology including pitching, Ground Crew, landing sequences, and promotional materials, and landed the Mission on our Product and Engineering All-Hands Offsite. After three months under the new reorganization it was time to measure how we were doing.</p><p>We approached it similarly to measuring any other Mission. We needed to look at the usage, the conversion rate, and the error rate or user comfort. We needed to define the metrics on SpaceUP as well.</p><h3>The Survey</h3><p>We choose to first focus on likes, dislikes, and level of satisfaction with the overall SpaceUP methodology. Second, we examined things like individual rituals, processes, and Mission phases from the perspective of SpaceUP’s goals, including having more time to focus, feeling of ownership, and teams’ capacities. Finally, we addressed issues that were brought up during 1:1s, such as problems not being addressed, and lack of 1:1s structure. This last part was very similar to standardized HR questionnaires measuring employee engagement.</p><p>One of the objectives we set at the beginning was to be able to track how successful we are in reaching our goals. That influenced the wording of the survey, to be timeless and general enough that it won’t matter if a respondent fills it in now, or in half a year.</p><p>We collected all the questions and topics from key stakeholders, reviewed a few iterations of the questions and options and in the end implemented the survey in SurveyMonkey. To ensure the answers were anonymous and everyone could respond as open and honestly as possible, we distributed it in multiple Slack channels using a link rather than via email.</p><h3>What We’ve Learned</h3><p>Of the roughly 160 colleagues in Product and Engineering, 108 filled out the survey. They spent typically around 30 minutes on it, and 88% of those who started finished the whole survey.</p><p>Overall, 64% of respondents reported that they liked the SpaceUP methodology, especially that they had more focus to work on the product, felt more ownership and responsibility, more transparency and visibility of our work, and liked the concept of Missions. And, of course, they liked the visuals and theme of SpaceUP. Those who rated the whole SpaceUP methodology highly also tended to follow the rituals, processes, and Mission phases more carefully.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*KqMYB0u19RdmDNS2x7cpow.png" /><figcaption>We do like SpaceUP, and some of us don’t know yet.</figcaption></figure><p>Those who didn’t like it cited problems in the Ground Crew such as too few people, being on Ground Crew for many weeks in a row, or that it’s hard to hand over knowledge to other colleagues. Some mentioned that they believed the Mission pitching felt too bureaucratic, low capacity of the team, and unclear terminology and methodology of SpaceUP.</p><p>We had 63% of colleagues flying at least one Mission and 60% spent at least one week at Ground Crew supporting customers and fixing bugs.</p><p>Even the understanding of the company’s vision and mission was rather high, with around 80% agreeing that they know and understand it. Not surprisingly, a solid understanding of the company’s vision and mission correlated with respondents being comfortable trying new things and driving innovation, and vice versa. In Spaceports without clear objectives, respondents avoided trying new approaches and taking risks.</p><p>On the other hand, <a href="https://medium.com/ataccama-spaceup/chapter-5-societies-circles-not-yet-another-product-andengineering-matrix-structure-11fdd1b0bb69">our Circles</a> (groups of people organized around a specific area of expertise) didn’t receive much improvement since the initial reorganization, and 56% of our colleagues found it the same as before. The most common comments were that there was not enough transparency about what different Circles focus on, and some of them were perceived as not so active.</p><p>In general, the feedback was great. However, the survey was quite long, so we will repeat it only once every 6 months. The respondents appreciated the survey and that the company is listening and taking responsibility.</p><h3>The Changes in SpaceUP</h3><p>After collecting and analyzing all the data, we shared it in two phases. First, the key problems were addressed on the Product and Engineering All-hands. Two weeks after the survey ended we introduced the team to the steps we will take to address these problems.</p><p>Second, we shared a slide deck with all the data explained, as well as the whole data set for those who wanted to deep dive into topics of interest.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*CyVny4Note2WY4RBgWAPmA.png" /><figcaption>Full slide deck shared with the whole team with complete survey results.</figcaption></figure><p>Based on the feedback from our colleagues we focused on changing these areas:</p><ol><li>Making the Mission process less bureaucratic and asynchronous</li><li>Doubling down on hiring (and our referral program, which just recently received third place for Referral Program of the Year by the Recruitment Academy Awards in Prague)</li><li>Improving how Circles work, setting clear goals, and promoting them within the organization.</li></ol><h3>Wrap-Up</h3><p>Yes, SpaceUP is working. But as with all products, we need to measure, learn, iterate and improve what we started. We were excited and overwhelmed by such a high response rate, comments that were on point, and the time that the team invested into this survey. Metrics aside, this tells us that our team cares and wants to participate in the changes. We will repeat the survey in the summer and see how the recent changes work.</p><p>Want to learn more about SpaceUP? Read our <a href="https://medium.com/ataccama-spaceup/spaceup-inspiration-talking-tribes-missions-with-tomas-rehor-701720668cab">previous interview with Zenbase’s Tomas Rehor</a> to see how we found inspiration for our new framework. Or, why not start at the beginning with <a href="https://medium.com/ataccama-spaceup/chapter-1-does-it-scale-why-were-rethinking-our-engineering-and-product-organization-93135018aac5">Chapter One</a>!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d8a552f25380" width="1" height="1" alt=""><hr><p><a href="https://medium.com/ataccama-spaceup/improving-the-methodology-how-we-collect-feedback-to-get-better-d8a552f25380">Improving the methodology: How we collect feedback to get better</a> was originally published in <a href="https://medium.com/ataccama-spaceup">Ataccama SpaceUP</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[SpaceUP Inspiration: Talking Tribes & Missions With Tomas Rehor]]></title>
            <link>https://medium.com/ataccama-spaceup/spaceup-inspiration-talking-tribes-missions-with-tomas-rehor-701720668cab?source=rss----20007d403983---4</link>
            <guid isPermaLink="false">https://medium.com/p/701720668cab</guid>
            <category><![CDATA[scaleup]]></category>
            <category><![CDATA[mission]]></category>
            <category><![CDATA[spaceup]]></category>
            <category><![CDATA[engineering]]></category>
            <category><![CDATA[product-management]]></category>
            <dc:creator><![CDATA[Natalie Miller]]></dc:creator>
            <pubDate>Thu, 31 Mar 2022 16:39:09 GMT</pubDate>
            <atom:updated>2022-04-01T11:40:58.257Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*aT2v352jDOH48Ji1SeYF7A.png" /></figure><p>Tomas Rehor has worked and led in some of the most notable tech companies including Skype, Microsoft, and Kosik. Now the CTO of American-based startup Zenbase, Tomas is building their R&amp;D from Prague and scouting for talent to join the new team.</p><p>As the former Head of Engineering and first employee in Pipedrive’s Prague development center, he not only grew his team in terms of size, but created a methodology of approaching work that completely changed how they viewed and delivered projects. This Tribes &amp; Missions concept Pipedrive adopted was a major inspiration for our SpaceUP methodology at Ataccama — and what better way to learn from previous iterations than to hear from the expert who consulted with us before starting this journey.</p><p>We sat down with Tomas to pick his brain about his experience with Tribes &amp; Missions, what’s changed since he first started using it, and why it might be time for you to rethink your team structure, too.</p><p><strong>Hi Tomas! To get started, could you explain what Tribes &amp; Missions are?</strong></p><p>The main idea is to group people together in bigger groups–we call them Tribes–and it should resemble a group of different people living together and working on the same agenda. You can imagine a Tribe as a group of 20 to 25 people with different skill sets, and they’ll have all the skills needed to run a part of the product or the whole product. It would have product managers, product designers, and all kinds of software engineers that you need and the Tribe delivers end-to-end functionality of what it owns.</p><p>Then, you need to have business ownership. The Tribe owns a very well-defined part of the product end-to-end, meaning as long as they follow the general company strategy and contribute to the common KPIs, they are free to choose how they deliver. That’s why it’s important that there is strong product ownership within the Tribe, who actually decides the strategy, and the engineering is there to deliver.</p><p>Then the second part is the types of Missions — how do you deliver once you decide what to deliver? How to deliver most efficiently and sustainably, as the number of your teams grows it’s impossible to deliver sustainably, the delivery pace slows down and motivation goes down.</p><p><strong>How big was the Pipedrive team when you joined, and when you left?</strong></p><p>In Prague it was one when I joined and 45 when I left. And the entire company was just over 300 when I joined, and close to 900 when I was leaving.</p><p><strong>Most product companies use Scrum. Why should a company consider a fundamentally different approach, like Tribes &amp; Missions?</strong></p><p>I don’t think they are 100% substitutes for each other. For me, Scrum is a way for a single team to organize their way of working and delivering a feature. So you can be on a Mission and the team can decide to use Scrum.</p><p>If we think about structuring teams, when they chose to reorganize how we worked, we were solving a problem. This problem was that they had 17 traditional Scrum teams each working with very strong ownership of an area. This meant that whenever you needed to deliver a bigger initiative spanning across the entire product, you’d need easily six or seven teams cooperating together. They soon realized they weren’t able to innovate fast enough or deliver new features.</p><p>A project that would have taken a month to complete would take easily up to a year because of the cross dependencies. You have a team wanting to deliver something they handed over to a different team, then they realize that it’s not exactly what they needed. So they come back to the team, who’s already working on another project. Then they need to wait for another sprint to start. I call it “dependency hell” because I’ve been there. It’s frustrating for any team to have to sit and wait for somebody else to deliver for you. Naturally, you don’t sit and do nothing, you work on something that’s not a priority for the whole company. You just kill time.</p><p><strong>Why is it important for people to have end-to-end ownership in their work?</strong></p><p>From my perspective, this is a fundamental question of motivation. If I believe in my skills and my capacity to help the company grow, it’s super frustrating if somebody tells me what to do and what not to do. On the other hand, I’m motivated when my ideas are supported and I’m being helped to implement what I think I’m good at. That’s my personal experience about what keeps people motivated. If you give them room to do what they’re best at, they will thrive — they will grow, they will blossom, and they will be super happy.</p><p><strong>It must give people a sense of duty and confidence to grow in their particular area.</strong></p><p>Yes, for me as a leader, or manager in traditional terms, it almost feels like cheating. When you give people room to grow, give them nutrients and water them when needed, they do it on their own. It’s like magic.</p><p>But it’s also super scary because you let go of control and believe people will do things right. And you need to implement other means of performance management or making sure that the right people are getting promoted, that people who are maybe underperforming get the right feedback. You have to do it differently, and I think that’s why it’s so scary and only a few enlightened companies have started the journey. And we can see it with COVID. I honestly didn’t think so many companies would force people to go back to the office. I think it’s a similar symptom that people are afraid to let go of control of the people they’re managing.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/480/1*toyuLRaifDCuVYkh3PdmnA.png" /><figcaption>Tomas presenting Tribes &amp; Missions at WebExpo.</figcaption></figure><p><strong>If we step back a bit to when you were at Pipedrive, what triggered the realization that you needed to change how you were working?</strong></p><p>Those 17 teams were rigid in their structure and scope of work and very interdependent. There was a constant struggle between different product managers to weigh their projects in other teams’ backlogs. It creates a stressful environment, and at the same time, the team feels they can’t deliver what they want because they are constantly blocked.</p><p>It’s mostly a feeling that something is not right in the company. But it’s very hard to measure at first. One thing that was measurable was that people started leaving. For the first time in Pipedrive’s history they had negative growth, and that was when they decided to sit down and rethink things. At this time, the engineering team had a little over 100 engineers and a proportionate size of product managers and designers. It was quite sizable, but not as big as when I left. So that was a trigger point, when the NPS score was bad and people started leaving.</p><p><strong>How long does it usually take for software engineers to adjust to something like Tribes and Missions if they’re already familiar with Scrum?</strong></p><p>We started with one or two Tribes, let them work for a month and learned from how they work, then we transitioned others. In terms of the way of working, it’s different. In a smaller team the scope of your domain you need to understand really well is quite narrow. With the Tribe, it multiplies. One of the biggest challenges is that people should be willing to learn new things quickly, and maybe not as in-depth as they’re used to. They should learn enough to fix bugs or write new code. If they need to understand some deeper or fundamental architectural decisions, they would know who to ask.</p><p>That was the biggest resilience I saw, that people no longer understand everything going on in that Tribe. And the purpose was not to have everybody understand everything. Some Tribes owned easily 30–40 services, so it’s hard to understand each. We wanted to nurture an open mindset. On a Mission, maybe two people already understand it, and two people are new to it and they figure it out on the way. At the end of the Mission, four people now understand this service. They return to the launch pad and spread this knowledge and on future Missions there is more mixing and matching.</p><p><strong>Do you think this type of methodology would work for companies that are not SaaS?</strong></p><p>I know of one Czech bank that transitioned but I don’t know how it turned out. My friend who worked there quit because he thought the transition was going too slow. But I think it fits any model or type of company. The only limiting factors are people. When he described the transition in this bank, the main problem he described was actually changing people’s mindset.</p><p>The traditional managers were used to a very top-down management structure. Basically, they like control. When somebody comes in and says they’re going to change everything and restructure, that kind of leaves this top manager hanging. There is very little room for traditional mid-level and upper management in this type of system so they fight against it. It is not transparent that somebody is blocking it but they will silently block any progress and change.</p><p><strong>At what point of a company’s lifespan do you think that they should consider adopting a new methodology?</strong></p><p>One important aspect of Tribes and Missions is separating deep focused work, when you are building new things and you need to really focus, from ad hoc work. When you’re writing code, especially something new, I think statistics show that you spend only 20% of the time actually writing the code and 80% time thinking about it. So you are mostly reading code, drawing on a whiteboard, talking to people and wrapping your head around the problem. This requires deep work. The moment somebody asks you to pull data from a database or asks a customer support question, the context and focus are lost.</p><p>In Pipedrive when we switched from the typical team setup to Missions, the first Mission team actually finished in 50% of the allocated time. Before, they were trying to work on 10 work streams at the same time with just six people, in addition to fixing bugs and the operational issues. So we assigned two people to work on operational stuff, and four people focused on new feature work. Then we can afford to work on four streams at once, and put the other six on hold. As a result, we could deliver much more in the same period of time. Long story short, I think even in a team of six, separating your operational work from focused feature work is already beneficial.</p><p><strong>Do you think Tribes and Missions help connect product, UX and engineering?</strong></p><p>Absolutely. What I’ve seen fundamentally broken is collaboration with the design team. In many companies, the design team works completely separate from the product teams, like an internal agency. They are given some design tasks, and they have their own opinion about how things should be designed. They delivered something maybe half compliant with the product manager’s requirements, and wasn’t consulted with engineers. The engineers say it is impossible. Then there’s more back and forth, and the design team becomes another dependency to fight for.</p><p>We ended up having the engineers design the solutions themselves, and it was crap simply because we didn’t have the design resources at the right time. So when you put the designers in the Tribe, and you make everyone live and breathe together, the outcomes are incredible. It worked really well in Pipedrive. If there were issues, it was typically misalignment of the organization between the engineering and product side. It’s super important to have them all together, and the more roles you can attach to a Tribe, the better.</p><p>It was totally mind opening for me when we started having a dedicated product marketing person planning with us. From the moment we started planning to deliver a new feature he was already planning the marketing campaign and using market insights in the planning process. We basically designed the product for success from the beginning, already knowing how we’re going to market it, how we’re going to launch it, what the stages are.</p><p><strong>Have you changed any of your original thinking or structure of Tribes and Missions?</strong></p><p>The main pillar of the original philosophy remains unchanged, but many practical things have evolved. We narrowed down the ideal Tribe size to 15 to 25. If it’s too few, you lose flexibility in terms of shifting priorities and allocating people to initiatives. If it’s too many, then the cognitive load is too big for people.</p><p>Then we looked at how we approach planning. You are always trying to predict the future and you always inevitably fail. At the same time, everybody around you expects you to put a stake in the ground and that that becomes the Holy Grail and source of truth, this release date. And this is probably the biggest stressor for everybody involved.</p><p>When we started Missions we said that we don’t want to plan the duration in the traditional way, and instead use the time box approach. Say we want to allocate six weeks for a project, and deliver as much as we can in six weeks. However, since people worked in traditional Scrum teams for too long, they didn’t switch their mindset to the time box method. They felt like it’s a deadline and they were working long hours to make it.</p><p>Only after talking to people after a few Missions, the pattern emerged that they are stressed about finishing on time. So we stopped using the word “timebox” and we decided to make an estimate after starting the Mission. We spend the first week trying to understand everything, discover all the unknowns, uncover the risks, then make the best estimate of when the Mission may end.</p><p>At the same time, some liked having an estimate for making decisions. You give the team flexibility, tell them what to deliver, give the context, how to measure success, what the business impact will be, and ask when they can deliver a meaningful version of it. They don’t need story points or anything measurable at first. We trust that they will deliver as fast as they can.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/480/1*sdNGEkvvU3dctPZE1o6iGg.png" /><figcaption>Co-creating SpaceUP at Ataccama’s Engineering Offsite in October</figcaption></figure><p><strong>From what you’ve seen, what do you think about Ataccama’s SpaceUP so far?</strong></p><p>I think SpaceUP is a very well-thought-out evolution of Tribes &amp; Missions and similar frameworks. It takes inspiration from what worked well and improves what didn’t, like alignment between engineering and product organizations.</p><p>I admire the level of detail used to describe every aspect of the framework and the discipline put into documenting everything publicly right at the beginning. Having well articulated principles written down helps with general understanding and reasoning. It also helps other companies who would want to take inspiration.</p><p><strong>Any advice for keeping on the right track with our Spaceports and Missions?</strong></p><p>I think the best advice is to listen to feedback, learn from mistakes and constantly adapt. Frameworks like this tend to be lively organisms and they never work perfectly from the beginning. While keeping the principles in place, it should be possible to adjust other parameters to make the framework perform optimally over time.</p><p><strong>What are your key takeaways from Tribes &amp; Missions?</strong></p><p>My key takeaway is that it really works and I think it really scales. It’s basically leveraging the way people naturally think and work, and putting it on scale. The principles can stay the same, and just adjust the teams. I’ve seen it grow in a company from 300 people to 900 people. We had eight Tribes at first and 20 plus Tribes when I was leaving, but the process was the same.</p><p>As I said, as a leader in this type of organization, it feels like cheating because it’s really effortless. The biggest part is to let the control freak in you go to bed. And then magic happens.</p><p><strong>What’s your next big goal?</strong></p><p>My next big goal is to build my own company from the ground up on these principles. And I’m very close to that. Zenbase is not my company, I’m a non-founder, CTO. But I’m the second person to be hired. So we’re really there from the ground up and I have a huge influence on how this company is being built, so that’s that’s my goal. Use this principle to build an entire company like this and hopefully see it flourish.</p><p>Want to learn a little bit more about SpaceUP? Read <a href="https://medium.com/ataccama-spaceup/chapter-6-from-iterations-to-tangible-results-mission-lifecycle-58f0c0e6871">Chapter 6 — From iterations to tangible results: Mission lifecycle</a> to see how our Missions and Spaceports work, as told by our VP of Product Management Tomas Porazil.</p><p>Brand new to SpaceUP? There’s no better place to start than on the first chapter! Head over to <a href="https://medium.com/ataccama-spaceup/chapter-1-does-it-scale-why-were-rethinking-our-engineering-and-product-organization-93135018aac5">Chapter 1 — Does It Scale? Why We’re Rethinking our Engineering and Product organization</a> by our VP of Product Strategy Martin Zahumensky to get up to speed.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=701720668cab" width="1" height="1" alt=""><hr><p><a href="https://medium.com/ataccama-spaceup/spaceup-inspiration-talking-tribes-missions-with-tomas-rehor-701720668cab">SpaceUP Inspiration: Talking Tribes &amp; Missions With Tomas Rehor</a> was originally published in <a href="https://medium.com/ataccama-spaceup">Ataccama SpaceUP</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Chapter 6 — From iterations to tangible results: Mission lifecycle]]></title>
            <link>https://medium.com/ataccama-spaceup/chapter-6-from-iterations-to-tangible-results-mission-lifecycle-58f0c0e6871?source=rss----20007d403983---4</link>
            <guid isPermaLink="false">https://medium.com/p/58f0c0e6871</guid>
            <category><![CDATA[process-improvement]]></category>
            <category><![CDATA[product-development]]></category>
            <category><![CDATA[agile-development]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[scaleup]]></category>
            <dc:creator><![CDATA[Tomáš Porazil]]></dc:creator>
            <pubDate>Wed, 23 Feb 2022 10:25:01 GMT</pubDate>
            <atom:updated>2022-02-23T10:25:01.166Z</atom:updated>
            <content:encoded><![CDATA[<h3>Chapter 6 — From iterations to tangible results: Mission lifecycle</h3><p><strong>Previous chapter: </strong><a href="https://medium.com/ataccama-spaceup/chapter-5-societies-circles-not-yet-another-product-andengineering-matrix-structure-11fdd1b0bb69">Societies &amp; Circles: not just another Product and Engineering matrix structure</a></p><p>If you’ve been following our SpaceUP journey, you are now familiar with why we have changed our product and engineering organizational principles. Before the reorganization, like millions of others we were using scrum and its ceremonies to keep ourselves organized. Currently, the concept of Missions are the mechanism how we add the value into the product. Even though we might use different terminology than you are used to, you will see in the following lines that the essence of ideas mentioned in the agile manifesto is in the core of our Missions.</p><h3>Aligned autonomy</h3><p>It is always tough to find a balance between autonomy and alignment. Some people even think that too much alignment removes the autonomy, and vice versa. We don’t agree with this, and as stated on a well-known image from Spotify, alignment enables autonomy. Especially, when we talk about companies that want to scale as we do, the holy grail is to find a way to achieve aligned autonomy. To get into this desired state we have defined a couple of stages which every Mission has to go through.</p><h3>Not everything is a Mission</h3><p>It may or may not be evident on first sight, but not every development effort has to be a Mission. We use common sense to distinguish between the Ground Crew and the Mission, but basically we follow these simple rules. Something is a Mission if any one of these apply:</p><ul><li>It’s a more significant investment in terms of man-days. We leave it up to one’s judgment but for me it means when something is more extensive than two people for two weeks (= 20 man-days).</li><li>It is a strategic decision about how we do something which deserves a broader discussion and alignment.</li><li>You need focus time to deliver it on schedule, e.g. because it was promised for some release.</li><li>It’s a cross-Spaceport effort which needs to be coordinated.</li></ul><h3>Mission lifecycle</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*O97tTwn0tMOtZd6VQ8usCQ.jpeg" /></figure><h4>1. Discovery</h4><p>The goal of the discovery is to find a product increment which is aligned with our product strategy captured in a Spaceports’ OKRs, and to ensure that risks are tackled upfront rather than at the end. The further you are in the development process, the higher the costs. By risks, we mean value risks (whether customers will buy it), usability risks (whether users can figure out how to use it), and feasibility risks (whether our engineers can build what we need with the time, skills, and technology we have).</p><p>How all the things above are tackled is the responsibility of the discovery team which nominates itself from the Ground Crew. The discovery is usually started by the product manager alone but very soon she joins forces with a product designer and a technical lead. This trio forms the core team who ideally flies the Mission once it gets approval. Does the initial team always consist of these three roles? Of course not. It should consist of roles which are needed to tackle and minimize risks mentioned above.</p><p>The tools and techniques which the team uses in this phase are quantitative and qualitative user and market research, running a series of very quick experiments with various types of prototypes.</p><p>It’s important to say, we don’t plan the discovery work on the Mission Control HQ level (more about the HQ later in this article). By its very nature, it is an activity with uncertain length and outcome and therefore very hard to plan. It is totally okay if the discovery ends up with the resolution that we don’t want to pursue the particular opportunity, which can happen for various reasons. It’s always better (cheaper) to kill something at the beginning before significant investment was put into it.</p><h4>2. Mission pitch</h4><p>The Mission pitch is the ultimate outcome of the discovery phase which has a form of a written document reacted collaboratively by the discovery team.</p><p>We believe that great communication is key ingredient for building stellar products. If you can’t formulate and capture your ideas in the form which is at the same time simple enough that everyone can digest it and still incudes all the critical parts, there’s a very small chance your ideas will stick and resonate. This is what makes a difference between great and good product leaders.</p><p>This sounds scary, but it doesn’t have to be. In Ataccama, we believe that everyone can formulate an idea and should be able to pitch a Mission. We encourage everybody to do so and the Mission pitch is here to help.</p><p>The Mission pitch is a structured document (a template) which provides a guide to tackle the most important product questions upfront. It consists of the following three main parts.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5yviG2AFCdityZgT0xuhcg.jpeg" /><figcaption>An example of a fat-marker sketch</figcaption></figure><p><strong>Problem</strong> When you write the pitch, you have to think about why the particular thing is actually a problem for your users and what is the benefit of solving it. It helps to imagine how the world will change when the mission successfully lands. In other words, what is the desired outcome to pursue.</p><p><strong>Solution</strong> A conceptual fat-marker sketch to ensure there is a feasible answer for the given problem. What also helps to shape the scope is to think about the paths which we don’t want to take and mark the problems which we don’t want to tackle. We call it Mission boundaries.</p><p><strong>Mission needs</strong> It represents the expected Mission duration with needed capabilities possessed by the Mission Crew. Rather than giving estimates, we frame the Mission in the form of the investment which which we are willing to spend for solving the problem — we set the appetite. Because every mission is kind of a bet, we defined the maximum length to eight weeks to minimize the risk of a wrongly-shaped Mission.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Sk13DTOl7b0R9iaWT1XwAg.png" /></figure><h4>3. Mission Control HQ</h4><p>Every Mission pitch is publicly presented to the Mission Control HQ, which consists of all Spaceport Leaders, Society Leaders and the CPTO. Who presents the pitch isn’t formerly defined but usually it is a product manager or future Mission Commander. There’s no need to use a special slide deck, and presenters are rather encouraged to present the authentically written Mission pitch in a concentrated form to ideally make it in the timeframe of five minutes. After all, it should be a pitch, not a meetup talk. The goal is to convince the audience that the problem is significantly large, the thinking is aligned with our product strategy, and there is a feasible solution.</p><p>After the pitch is presented, there are three types of possible feedback to receive. First, the Mission is approved and the team may proceed to the next phase. Second, there are still fundamental aspects and key questions to answer to better define the Mission outcome or to minimize the risks. In such cases, the team will work further on the Mission and pitch it again. Third, the pitch is rejected. Most of the time this happens when the targeted problem or the solution isn’t aligned with our strategy. Nevertheless, these discussions are very important for us because they open fruitful conversation which help us to better formulate our overall vision.</p><p>Are you asking yourself why do we need such a mechanism when we have autonomous Spaceports with defined objectives? Why can’t we leave it up to them and keep them accountable for fulfilling their goals? Most of the time we can and we do. However, there are moments when Mission Control HQ plays an irreplaceable role. One of them are cross-Spaceport Missions which wouldn’t be possible to coordinate, and the other are requirements to support crucial projects for our customers. In other cases, the HQ just oversees all ongoing Missions and from time to time adjusts the product strategy.</p><p>The key purpose of this phase is to ensure the alignment with product objectives, and to provide a transparency through the communication channel to other parts of the company so they know what to expect from the product organization.</p><h4>4. Assembling Mission Crew</h4><p>Every Mission is different, needs different skills, capabilities, and even different seniority level. Therefore we establish the Mission Crew for every new Mission. In the past, when we had stable teams it happened that we shaped the work around the team and its skills and capacities. If you think about it, that doesn’t make any sense and it should work vice versa. If there is work for three people for three weeks, why artificially adjust it so it fits in two-week scrum sprints of the team of seven people?</p><p>Usually in this phase, we enrich the core team which is typically ready from the discovery phase. This was the team who put together the whole Mission scope and presented it in front of Mission Control HQ during the Mission pitching. We try not to break this trio because during the work on the Mission pitch they have already created the tacit knowledge which is impossible to share and will help them during the flight. One person (astronaut) can’t fly two Missions at the same time. The Mission Crew has to be staffed so they are able to deliver the whole Mission on their own without any other dependencies and waiting times.</p><p>The Mission Commander plays a crucial role among the Crew Members as the smooth running of the Mission is their responsibility. They are the one who reports a Mission’s progress to a Spaceport Leader and removes all impediments. The Mission Commander can be anyone from the crew and it depends on the character of the Mission. Most of the time, it is a product manager, but if the mission is rather technical it can be one of the developers, or if it is oriented on improving the user experience, it can even be a designer.</p><p>When we put the Mission Crew together we think about the knowledge transfer and the personal growth of individual team members. Developers, designers and the product manager shouldn’t be part of the Mission Crew because some Deus ex machina assigned them there, but because they believe in the Mission’s success and want to contribute to it. Self-motivation and commitment are the cornerstones of Mission success.</p><h4>5. Pre-flight</h4><p>A final confirmation before the flight. At this moment, the Mission Crew is finalized and the Mission Commander is known. All of them should now have their full focus on the Mission without any other distractions. You can think of this phase like the Sprint Zero which is still happening on the ground. As we don’t want anyone to die in outer space, this is the last check before lift off. Each member of the Crew has to fully understand the given problem and desired outcome together with the high-level solution, including the architecture. This is a last resort for the team to challenge the Mission scope and the provided resources before they fully commit to a successful delivery.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*U1L_9mrBYT6eBG448nTsPw.png" /></figure><h4>6. Mission spacetime</h4><p>Finally, the dedicated time in which the product increment is materialized by the Mission Crew. During this phase, a production code is created. We call it spacetime not only because we like the analogy of a spaceship on the journey. But we also want to create a feeling that astronauts aren’t reachable because they left Earth and we can only contact them from time to time by a walkie-talkie. The only priority of the team in this phase is successful landing. Having an undisturbed time without distractions is one of the ways to help the team achieve it.</p><p>In reality, the team is separate from the Spaceport and most of its ceremonies for the duration of the Mission. The Spaceship crew is self-organized and has its own meetings. There isn’t any prescribed methodology and it is up to the Mission Commander whether the team will use Scrum, Kanban, or something completely different.</p><p>The only required contact with the Spaceport is during regular check-ins where the Mission Commander informs a Spaceport Leader about the progress. How often the contact happens is up to the Spaceport Leader and Mission Commander to decide. During their periodic conversations they may discover that the Mission isn’t on track for various reasons and that it doesn’t make sense for it to continue. Some Missions can and will crash, and there isn’t any shame in that. It takes courage but it’s always better to stop something sooner than later when there isn’t a chance for the Mission to land successfully.</p><h4>7. Mission landing sequence</h4><p>One of the key pillars of the SpaceUP is that each Spaceport is responsible for the end-to-end ownership of components they develop. Each Spaceport owns its part of the product. And the product doesn’t consist just of the code behind the running software but also from the documentation, marketing materials, training materials, demo content, and much more.</p><p>Therefore the landing sequence serves two purposes. First, to verify the quality of the delivered outcome — to check whether the technical/design debt is reasonably high so it can be tackled by the Ground Crew. Let’s face it, there is always some debt. Something to consider is whether the debt is low enough for the Ground Crew can manage it, or whether the Mission should be prolonged because defined outcomes or code quality standards haven’t been met. It can’t happen that the feature is merged before the product manager, designer, and technical lead see it. The product manager judges the business perspective, product designer checks or even tests the quality of delivered screens and interactions, and last but not least the technical leader verifies the standard of delivered code.</p><p>The second purpose is to ensure that all communication materials were properly created and nothing prevents our consultants or customers from benefiting from a newly developed feature. In the past, we often forgot to provide all needed materials, therefore we created a Mission landing checklist to forestall such situations. Before the spaceship lands on Earth and the Mission Crew declares the mission completed, they have to go through this checklist.</p><h4>8. Mission decommission</h4><p>We have a constant desire to improve as people, as professionals, and as a company. And it’s with this same mindset we approach Missions. Before the Mission Crew dissolves to the Ground Crew, there is one last thing they have to do, and that’s to reflect on what we learned during the Mission so each future Mission can be better than the previous one.</p><p>The Mission Commander organizes a retrospective, or if you want a post-mortem, to gather honest feedback from the whole crew. Learnings from the retrospective are then shared with the entire Spaceport but also across Spaceports through Circles. These learnings consist of information regarding organizational aspects such as communication, meetings, or various artifacts (e.g. how to improve the Mission pitching template), but also includes lessons learned from the technical solution. Decommission is for both the Missions which landed successfully but also, and maybe more importantly, for the ones that crashed.</p><p>The Mission Crew should now stay on Earth as part of the Ground Crew to enjoy some rest as especially the final stage of the Mission can be quite stressful. Moreover, this is another and natural way to spread knowledge about what was happening on the Mission and also how to pay the technical debt which could be created during the flight.</p><h3>To sum it up</h3><p>In our case, well-executed Missions help us with:</p><ul><li><strong>Transparency</strong> → Things which people are preparing are visible not just within a small team, but for the whole company; it opens good discussions.</li><li><strong>Quality assurance</strong> → In the past, sometimes things which went into development weren’t well prepared. The result was features that weren’t useful, usable, nor feasible and very often the development took much more time than expected. In general, the quality of the prepared work has improved.</li><li><strong>Discovery VS. Delivery</strong> → Now, there is admitted time for the discovery phase. It’s easier to distinguish which phase of the lifecycle we are in.</li><li><strong>Getting feedback</strong> → Everybody is getting better through getting good feedback. This is now naturally happening and it helps us raise the quality bar in general.</li><li><strong>Improved communication</strong> → As people need to communicate more and present their work (usually multiple times) we are getting better and better at how we talk about our work, problems, business opportunities, and features.</li></ul><p>We tried to be as specific as possible but because we wanted to write just a reasonably long article and not the whole book, we had to omit a lot of details. In some of the following articles we want to also cover what tools we use to capture and track the Missions’ progress, or how we map our objectives to the Missions. Nevertheless, if you missed something or have a question, please contact us and we will be more than happy to provide further information. We are still learning every day and adjusting the whole process to best suit our needs.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=58f0c0e6871" width="1" height="1" alt=""><hr><p><a href="https://medium.com/ataccama-spaceup/chapter-6-from-iterations-to-tangible-results-mission-lifecycle-58f0c0e6871">Chapter 6 — From iterations to tangible results: Mission lifecycle</a> was originally published in <a href="https://medium.com/ataccama-spaceup">Ataccama SpaceUP</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Chapter 5 — Societies & Circles: not just another Product and Engineering matrix structure]]></title>
            <link>https://medium.com/ataccama-spaceup/chapter-5-societies-circles-not-yet-another-product-andengineering-matrix-structure-11fdd1b0bb69?source=rss----20007d403983---4</link>
            <guid isPermaLink="false">https://medium.com/p/11fdd1b0bb69</guid>
            <category><![CDATA[organizational-culture]]></category>
            <category><![CDATA[software-engineering]]></category>
            <category><![CDATA[engineering-mangement]]></category>
            <category><![CDATA[management-and-leadership]]></category>
            <dc:creator><![CDATA[Roman Pichlík]]></dc:creator>
            <pubDate>Thu, 27 Jan 2022 12:56:32 GMT</pubDate>
            <atom:updated>2022-01-28T13:05:27.292Z</atom:updated>
            <content:encoded><![CDATA[<h3>Chapter 5 — Societies &amp; Circles: not just another Product and Engineering matrix structure</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Jh43svlyh4BTSkG-yWybIg.jpeg" /></figure><p><strong>Previous chapters: </strong><a href="https://medium.com/ataccama-spaceup/chapter-1-does-it-scale-why-were-rethinking-our-engineering-and-product-organization-93135018aac5"><strong>Chapter 1</strong></a><strong> | </strong><a href="https://medium.com/ataccama-spaceup/chapter-2-spaceup-or-how-we-changed-the-way-our-product-engineering-works-41e302045b95"><strong>Chapter 2</strong></a><strong> | </strong><a href="https://medium.com/ataccama-spaceup/chapter-3-space-up-fundamentals-the-glossary-2a28f8d68e42"><strong>Chapter 3</strong></a><strong> | </strong><a href="https://medium.com/ataccama-spaceup/chapter-4-key-roles-in-the-organization-and-their-responsibilities-62a4d89a52a7"><strong>Chapter 4</strong></a></p><p>Welcome to chapter 5 of our SpaceUP series. In previous chapters, we covered the differences between <a href="https://medium.com/ataccama-spaceup/chapter-3-space-up-fundamentals-the-glossary-2a28f8d68e42">Spaceports and Societies</a>, how <a href="https://medium.com/ataccama-spaceup/chapter-2-spaceup-or-how-we-changed-the-way-our-product-engineering-works-41e302045b95">Missions help us achieve our objectives</a>, the purpose of the Ground Crew, as well as the <a href="https://medium.com/ataccama-spaceup/chapter-4-key-roles-in-the-organization-and-their-responsibilities-62a4d89a52a7">key roles </a>— Spaceport Leader, Mission Commander, Society Representative — and their responsibilities. Now, it’s time to focus on Societies and Circles, the pillars of cohesion among Spaceports.</p><h3>Societies</h3><p>This is where all the people with a common area of expertise connect. Currently, we have two main Societies: Product and Engineering. While Spaceports are more product-aligned verticals, Societies are more horizontal, crossing all Spaceports.</p><p>Daily life rituals and work among Spaceports can differ. To give you some examples: the newcomers’ onboarding may differ to some extent across Spaceports; Spaceports find their own way of doing retrospectives; Spaceports have office day(s) when they meet together or, conversely, hold no meeting days for an uninterrupted chunk of focused work, bug planning, and paying off technical debt. That’s the purpose. Giving each Spaceport enough autonomy to tackle problems on their own.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/398/1*P0EMSqN5ujo-Z4suq3vjYw.png" /></figure><p>On the Society level, people live more like a community, with common denominator standards. A Society guarantees people are treated equally, regardless of which Spaceport they currently belong to.</p><p>Societies ensure people are having 1:1s, personal growth plans, proper training, etc. A Society defines the interview process and sets requirements for candidates to fulfill, regardless of their future Spaceport placement.</p><p>To give you an example: The Engineering Society sets and owns engineering processes and the modus operandi, e.g. DevSecOps, on-call duties, combined engineering practices, release and testing practices to comply with company objectives, such as the transition to cloud, etc. A Society defines the job ladder, ensures people are promoted regularly, and keeps their compensation package (salary &amp; stock options) fair.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/398/1*HYaLL2nU0rheiOqPWEgBqA.png" /></figure><p>Reporting always follows an affinity to its Society. In other words, people and the managers they report to originate from the same Society, either Product or Engineering. While reporting within the Engineering society adheres to Spaceport affinity (your manager is from your Society and your Spaceport), reporting within the Product Society adheres to Circle affinity (your manager is your subject matter expert, e.g. a designer, UX researcher, etc.). This is up to the decision of a Society leader, either the Head of engineering or the Head of Product &amp; Design.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*StBJUFWuEs1zBsRgM9AMKQ.png" /><figcaption>Spaceports Reporting Structure</figcaption></figure><p>You may ask: isn’t this a matrix organization structure? And the honest answer: yes and we have good reasons for it. We don’t want to end up with a silo organization with something like 7 engineering organizations. We intentionally designed a setup that allows us to connect people from multiple Spaceports so they can share their experience and knowledge, help others, and agree on some company-wide standards. People can safely jump on/off to a Spaceport without feeling they settled on a different planetary system.</p><p>Conflicts. Conflicts happen all the time, regardless of organization structure. Societies are autonomous in defining their own reporting structures, standards and processes while Spaceports are autonomous in defining their inner processes for tackling product challenges. In case of conflict between a Society and a Spaceport, all Society and Spaceport leaders report to the same boss — the Chief Product and Technical officer, who has the last say in unresolved disputes.</p><h3>Circles</h3><p>This is a group of people organized around a specific expertise or capability within the Societies. Societies are big, and there are still multiple internal groups, each focusing on a different area of expertise. These specialized groups are called Circles.</p><p>A Circle covers one of the key capabilities a Society decides to drive top-down across all Spaceports, for example product quality, cloud-native systems, or UX research. Usually, there is a representative from each Spaceport within a given Circle, unless states otherwise (e.g. a UX researcher doesn’t make sense in a Cloud &amp; Infrastructure Spaceport). Spaceport representatives within a Circle are chosen based on a mutual agreement between a Circle leader and the Spaceport leadership.</p><p>Circles have power and autonomy to set their working habits, such as how often they meet, how exactly they tackle problems, and also their agenda. A Circle’s agenda is partially driven by the Spaceport’s needs, but also by objectives coming from the Society. These objectives are more high-level, like for example “Being a Kubernetes first-class citizen”, or “Shortening the release cycle”. The Society leader select Circle leaders. A Circle leader is an idea maker, an undoubted expert and a person who manages the Circle and has the final say. The Circle leaders set these objectives together based on the company objectives.</p><p>Circles have a strong impact on Society processes, such as hiring requirements, interview content, onboarding, training, or the feedback loop, but they also drive technology innovation and help tackle technology and architecture challenges ahead of us. To give you a couple of examples of what a Circle drives: Secure coding practices and Security training come from the Security Circle, and the Software Engineering Circle is focused on improving the developer experience, e.g. they pick a tool allowing engineers to better collaborate on technical debt.</p><h3>Wrap-up</h3><p>In this chapter, you’ve learned more about Societies and Circles and their role in the SpaceUP methodology. These organization horizontals hold people, processes and standards coherent across Spaceports — our product verticals. In the next chapter, you will learn more about the Mission lifecycle.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=11fdd1b0bb69" width="1" height="1" alt=""><hr><p><a href="https://medium.com/ataccama-spaceup/chapter-5-societies-circles-not-yet-another-product-andengineering-matrix-structure-11fdd1b0bb69">Chapter 5 — Societies &amp; Circles: not just another Product and Engineering matrix structure</a> was originally published in <a href="https://medium.com/ataccama-spaceup">Ataccama SpaceUP</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Chapter 4 — Key roles in the organization and their responsibilities]]></title>
            <link>https://medium.com/ataccama-spaceup/chapter-4-key-roles-in-the-organization-and-their-responsibilities-62a4d89a52a7?source=rss----20007d403983---4</link>
            <guid isPermaLink="false">https://medium.com/p/62a4d89a52a7</guid>
            <category><![CDATA[data-management]]></category>
            <category><![CDATA[scaleup]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[engineering]]></category>
            <dc:creator><![CDATA[David Kolínek]]></dc:creator>
            <pubDate>Tue, 18 Jan 2022 16:37:39 GMT</pubDate>
            <atom:updated>2022-01-27T15:01:54.462Z</atom:updated>
            <content:encoded><![CDATA[<h3>Chapter 4 — Key roles in our Product &amp; Engineering organization</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*EkgYDxV5eanuGaWGIa9ETA.png" /></figure><p><strong>Previous chapters: </strong><a href="https://medium.com/ataccama-spaceup/chapter-1-does-it-scale-why-were-rethinking-our-engineering-and-product-organization-93135018aac5"><strong>Chapter 1</strong></a><strong> | </strong><a href="https://medium.com/ataccama-spaceup/chapter-2-spaceup-or-how-we-changed-the-way-our-product-engineering-works-41e302045b95"><strong>Chapter 2</strong></a><strong> | </strong><a href="https://medium.com/ataccama-spaceup/chapter-3-space-up-fundamentals-the-glossary-2a28f8d68e42"><strong>Chapter 3</strong></a></p><p>After reading the first three chapters, you should now understand the differences between a Spaceport and Society, how we use Missions to achieve our objectives, and also know the crucial role of the Ground Crew.</p><p>Now it’s time to take a look at the most important roles so you have a good idea about the <strong>responsibilities and characteristics of each role</strong> that’s part of SpaceUP.</p><h3>Spaceport Leader</h3><p>A Spaceport Leader must be a <strong>strong visionary</strong> that can identify the biggest opportunities on the market and define a clear strategy for the Spaceport based on those inputs. It’s important for this person to be a <strong>team player,</strong> as we need all Spaceport Leaders to work closely together and define a strategy not only for their individual Spaceports, but for the entire Ataccama ONE platform.</p><p>Also, they have to be a natural leader who’s able to motivate people, bring them into the team and <strong>create an environment where they feel empowered and understand their purpose.</strong> The leader must also be an <strong>excellent communicator</strong> because it’s essential to be able to communicate the visions clearly both internally to the whole company, and externally to the market.</p><p>Last but not least, this person must have a <strong>strong focus on execution</strong>, making sure that everything the Spaceport is on the right path to fulfill the vision. Let me break down the responsibilities in greater detail:</p><p><strong>Product</strong></p><ul><li>Co-defining product vision with the rest of the <a href="http://heade/">Headquarters</a> team and defining the vision for their Spaceport</li><li>Defining Spaceport objectives for the next 12–18 months</li><li>Constantly flying Missions that help us achieve our objectives</li><li>Setting high standards for our product quality</li><li>Overseeing the quality of the resources (e.g. documentation, training materials, etc.) we provide together with the product</li></ul><p><strong>People</strong></p><ul><li>Staffing the Spaceport, hiring the best talent we can find</li><li>Building our team culture, making sure people are happy and enjoy being part of this team</li></ul><p><strong>Organization</strong></p><ul><li>Make collaboration within the Spaceport seamless and as effective as possible</li><li>Set the processes and ceremonies according to our current needs (e.g. growing team size, intense collaboration with other Spaceports, etc.)</li></ul><p><strong>Communication</strong></p><ul><li>Be the public face of our product, including public speaking, interactions with analysts, partners, etc.</li><li>Define clear communication strategy with sales and marketing teams</li><li>Internal evangelism so the whole company knows what’s happening with our product</li></ul><p>Sounds like too many responsibilities for one person? Sure, of course it’s impossible for one person to do all of this alone. That’s why the Spaceport Leaders <strong>rely on a small Spaceport Core team</strong> that consists of Society representatives and selected Tech leads, PMs, and Engineering managers. They help them to achieve everything I wrote above. In other words, while the Spaceport Leader is formally the one responsible for all those things, <strong>it’s the responsibility of the whole team</strong> and they work on it together.</p><h3>Is the Spaceport Leader the ultimate manager?</h3><p>You might think that all those 20–45 people in the Spaceport report to the Spaceport Leader, but it’s actually the opposite. <strong>The leader has zero reports — ZERO.</strong> And honestly, from the feedback we gathered so far, <strong>it’s the best decision we could have made.</strong></p><p>It’s impossible to imagine the leader would be able to find time for all the things described above and at the same time focus on people, having all those 1on1s, preparing individual plans, being there for them 24/7. It’s just not possible to do all of it. The leader would have to do one at the expense of another, which would be a ticking bomb that wouldn’t work in the long run. So we were looking for a different solution.</p><p><strong>People in the Spaceport are reporting to a Society Representative</strong> (either Product or Engineering Representative). They are the ones that have the final say regarding hire/termination competencies, they’re responsible for salaries, approving personal absences, or preparing individual plans for people so they know what they should focus on. But it’s done based on mutual discussion between both — they regularly talk about the performance of each individual in the team, their motivation and future career path, and try to align it with the needs of the Spaceport.</p><p>So while the leaders don’t have the formal reporting power and can’t fire anyone, or give them a raise, they <strong>actually have all the means they need</strong> and discuss all important decisions with their Society Representatives. Given the culture we have at Ataccama we’re always able to quickly come to a mutual agreement.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*qLAgtBQLnc-3TbA-_aYKrA.jpeg" /><figcaption>Picture from our Engineering Offsite where each Spaceport Leader was presenting the Spaceport vision</figcaption></figure><h3>Mission Commander</h3><p>Each Mission has a leader who’s responsible for its end-to-end execution. It can be anyone, not only a PM or Engineering manager, and <strong>it’s rather a role than a position</strong>. The best definition for this role is it must be someone with the mindset to <strong>get things done</strong>, a systematic and organized person that can bring the team together and always finds a way to overcome the issues that will surely appear during the Mission.</p><p>The Commander needs to make sure the Mission Crew is aligned and working together as a team, refinements are leading to a good solution, development is going well, testing is done properly, we are regularly validating the output with relevant stakeholders, etc. <strong>Commanders work with Spaceport Leaders all the time,</strong> as they need to know how things are going and whether there are some issues that they should know about or can help with.</p><p>Just to make sure it’s clear, the <strong>Mission Commander is not a manager of the Mission Crew</strong>. The main and only responsibility is the successful execution of the Mission, not people management.</p><h3>Ground Crew Leader</h3><p>There are so many things happening on the ground that it’s essential to have someone overseeing all of this, helping with the organization, making sure support is provided to other teams as quickly as possible, and also helping the Ground Crew with actively planning bigger improvements we want to focus on.</p><p>What qualities form a good Ground Crew Leader? It must again be a <strong>systematic person and a problem solver</strong>. Someone that can be the primary point of contact for other teams within the company, someone calm who can track and process all the requests coming in, and help the Ground Crew manage it with ease.</p><p>To give you a better idea about their responsibilities, here’s what a Ground Crew Leader manages:</p><ul><li>The incoming requests from professional services in Slack &amp; Jira</li><li>Facilitating task distribution (bug fixing, minor technical debt, or other types of unplanned work)</li><li>Releasing co-ordination and test execution by the Ground Crew</li><li>Selecting the main focus for the Ground Crew (test automation, UX improvements, focus on creating resources, supporting knowledge sharing, etc.)</li><li>Communicating with other Spaceport’s Ground Crews</li></ul><p>There are <strong>many similarities with the Mission Commander role</strong>. It’s a dynamic role, so we are rotating Ground Crew Leaders over time. The people in the Ground Crew don’t report to this person, and Spaceport Leaders regularly talk with their Ground Crew Leaders so they can discuss the progress, critical issues, and long-term focus.</p><h3>Society Representative</h3><p>Now, we get to the Society Representative role. <a href="https://medium.com/ataccama-spaceup/chapter-2-spaceup-or-how-we-changed-the-way-our-product-engineering-works-41e302045b95#ef6c">As you know by now</a>, we have 2 societies, Product &amp; Engineering, and <strong>each Society has one representative in every Spaceport</strong>. A Society representative is a person that helps Spaceport Leaders in 3 main areas:</p><ul><li>Make sure we have the <strong>best subject experts in the Spaceport</strong> and also propagate things defined on a Society level (e.g. development best practices, some engineering-wide standards, etc.) into our Spaceport.</li><li>Continuously improve our <strong>ability to deliver a great product, both in terms of speed and quality</strong>. They are helping with defining the processes, getting rid of roadblocks, and making the execution seamless.</li><li>Make sure <strong>people in the Spaceport have all the support they need</strong>. This goes from mentoring them and helping them prepare their individual growth plans to also helping them overcome their personal challenges.</li></ul><p>Their official job title is Director (e.g. Director of Engineering — Data Governance) so this might help you imagine what exactly they do and what their responsibilities are. It fits the traditional description of this role well. <strong>They work closely with Spaceport Leaders</strong>, they are the right hand person the leaders couldn’t live without. A common setup is to have regular weekly syncs and many ad-hoc conversations throughout the week. And as mentioned above, they play a crucial part in the Spaceport Core team.</p><p>They also <strong>work closely with their Society Leader</strong> (they are reporting to them). Together with the other representatives, they discuss the engineering-wide initiatives and what are the specific areas we’ll focus on, both long and short term.</p><p>A good Society Representative <strong>must put people above everything else</strong>. They must be <strong>empathic and trustworthy</strong>, so people can open up to them. They must be reliable so people can count on them and know they <strong>always have someone they can rely on</strong>.</p><h3>Society Leader</h3><p>The biggest challenge a Society Leader has is to <strong>create an environment that allows the Spaceport to be as independent as possible but at the same time make sure we are developing ONE platform. I</strong>t can’t be complete anarchy where each Spaceport is doing things completely differently. The Society Leaders <strong>set some basic rules and boundaries</strong> that have to be respected across the whole Product &amp; Engineering team, in order to keep the tech stack and developer experience sane.</p><p>So in short, everything described above regarding Society Representative responsibilities applies to the Society Leader as well, with the difference that the <strong>Society Leader is responsible for this globally, for all the Spaceports</strong>. The Society Representatives take care of execution in each Spaceport.</p><p>This also highlights the most important quality we need from the Society Leader — <strong>they must think globally</strong>. It’s important that they create an environment that will <strong>allow Ataccama to scale</strong> and prosper in the long term. They always <strong>have to be a few steps ahead</strong> and look for solutions to problems that are hidden around the corner.</p><h3>Chief Product &amp; Technical Officer</h3><p>The last role I haven’t talked about is the most important one. 🎉 💪 We have a new man in charge, <a href="https://www.linkedin.com/in/martin-zahumensky-1085582/">Martin Zahumensky</a>, and he is THE main commander of our whole space shuttle. 🚀 He already talked about <a href="https://medium.com/ataccama-spaceup/chapter-1-does-it-scale-why-were-rethinking-our-engineering-and-product-organization-93135018aac5#45ae">why we introduced this role in the first chapter</a>, the motivation behind it and the expectations, so definitely check it out if you missed it.</p><h3>Headquarters team</h3><p>I know this is not a role but I believe it’s crucial to mention it as well, otherwise it might sound like the Spaceport Leaders don’t actually work together. It’s in fact the opposite. The <strong>HQ team meets multiple times a week</strong> so things like operational issues, but also long-term strategy and the product vision, can be discussed.</p><p>We have all the Spaceport Leaders and Society Leaders there, and obviously the CPTO that’s leading this team. 💪 So while each of the HQ members are responsible for “their own thing,” it’s just a piece of something much bigger — our ONE unified platform. And the HQ team is the mechanism that allows us to achieve this. <strong>SpaceUp would not work without it</strong>.</p><p>We briefly mentioned who is reporting to whom but I expect you still have many questions about the reporting structure. We will cover it in detail in the next article, together with a detailed description of the Societies &amp; Circles. Stay tuned. 🍿</p><p><em>Would you like to know more about the specifics of one of these roles? Which one? Let me know in the comments! 📣 I would be happy to follow up with something like a “Day in the life” article to provide you with even more insights.</em></p><p><strong>More SpaceUP:</strong></p><ul><li><a href="https://medium.com/ataccama-spaceup/chapter-5-societies-circles-not-yet-another-product-andengineering-matrix-structure-11fdd1b0bb69"><strong>Chapter 5</strong></a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=62a4d89a52a7" width="1" height="1" alt=""><hr><p><a href="https://medium.com/ataccama-spaceup/chapter-4-key-roles-in-the-organization-and-their-responsibilities-62a4d89a52a7">Chapter 4 — Key roles in the organization and their responsibilities</a> was originally published in <a href="https://medium.com/ataccama-spaceup">Ataccama SpaceUP</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Chapter 3 — Space UP fundamentals: The Glossary]]></title>
            <link>https://medium.com/ataccama-spaceup/chapter-3-space-up-fundamentals-the-glossary-2a28f8d68e42?source=rss----20007d403983---4</link>
            <guid isPermaLink="false">https://medium.com/p/2a28f8d68e42</guid>
            <category><![CDATA[product]]></category>
            <category><![CDATA[scaleup]]></category>
            <category><![CDATA[agile-methodology]]></category>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[methodology]]></category>
            <dc:creator><![CDATA[Tomáš Porazil]]></dc:creator>
            <pubDate>Wed, 12 Jan 2022 22:01:22 GMT</pubDate>
            <atom:updated>2022-02-01T12:41:55.219Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5qm7UDO5vdv_Q9bdd0yYaQ.jpeg" /></figure><h3>Chapter 3 — SpaceUP fundamentals: The Glossary</h3><p><strong>Previous chapters: </strong><a href="https://medium.com/ataccama-spaceup/chapter-1-does-it-scale-why-were-rethinking-our-engineering-and-product-organization-93135018aac5"><strong>Chapter 1</strong></a><strong> | </strong><a href="https://medium.com/ataccama-spaceup/chapter-2-spaceup-or-how-we-changed-the-way-our-product-engineering-works-41e302045b95"><strong>Chapter 2</strong></a></p><p>This is a one-pager that summarizes its most important parts, and helps you understand the entire methodology at a glance. The glossary wasn’t intended to be an end in itself, we just wanted to solve a problem with it — but it ultimately turned out to be very useful.</p><p>As you might have already read in the previous articles, we introduced the entire SpaceUP methodology to our Product and Engineering organization with a bang. When you read about change management, making a lot of changes at once may sound like a silly idea. Nevertheless, given the circumstances and looking back, I think we’ve done quite a good job aside from a few details.</p><p>So, how did we do it?</p><p>First of all, we knew we needed everyone’s full attention, and we sensed it wouldn’t be possible through a Zoom call. Therefore, we decided to organize an offsite, take people out from their Covid-home-office comfort zones and bring them together in one place.</p><p>To demonstrate the kind of challenge we faced, I’ll never forget when Michal, our CEO, started the offsite by asking the crowd how many of them joined us during Covid. Roughly, it was half. Half the people had never even seen each other in person.</p><p>So, you have 180 people in the same room, full of expectations, and now what? We knew people couldn’t absorb everything simultaneously, all at once. If we helped them understand the main pillars of the new operating framework, we’d be successful. We decided to apply the Pareto principle, which states that roughly 80% of consequences come from 20% of causes.</p><p>We defined 20% of the crucial foundations, and the so-called “SpaceUP Glossary” was born. We printed it out and put it on every table, so everyone had a physical copy when they arrived at the offsite. Whenever someone got lost in all the newly-defined terms, they could use it as a reference. And that still applies today.</p><h3>Glossary</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/860/1*JkvHXyckSPbUJqno574Bqg@2x.png" /></figure><h4>Spaceport</h4><p>Each Spaceport has one clear purpose — to ensure end-to-end ownership of our product, even beyond software development. It’s a home base, a safe zone where teammates always have your back.</p><h4>Spaceport objectives</h4><p>These help Spaceports decide what they want to achieve, and what goals to set for themselves. The Spaceport’s objectives are also aligned with the company objectives and product strategy.</p><h4>Spaceport Leader</h4><p>Each Spaceport has one Leader. They’re ultimately responsible for the Spaceport’s success, from defining its vision and building the team, to successful product delivery. Leaders report directly to the CPTO and are part of Mission Control HQ.</p><h4>Ground Crew</h4><p>This group makes sure a Spaceport is up and running, supports customers, forms new missions, and improves the Spaceport’s quality by tackling technical debt, automating things, fixing bugs, and more. It’s not a permanent role, and members rotate between flying missions and being on the Ground Crew.</p><h4>Ground Crew Leader</h4><p>The person who oversees what’s happening on the ground, and helps keep things organized and in good shape. It’s more of a role than a position. Everyone’s encouraged to try being a Ground Crew Leader at some point.</p><h4>Mission</h4><p>Each mission brings us one step closer to achieving an objective. It’s a solution with a clear definition and scope, description of boundaries, expected landing date, and a dedicated Mission Crew.</p><h4>Mission pitch</h4><p>A structured proposal with a definition of the problem and a description of why solving it will help the Spaceport achieve its objective(s). Anyone can pitch a new mission — just prepare a high-level solution to a problem and present it to Mission Control HQ.</p><h4>Mission Crew</h4><p>A group of astronauts with the right skills that will fly the mission. Thanks to the Ground Crew, they won’t be disrupted by things happening on the ground, and their main focus is completing the mission on time.</p><h4>Mission Commander</h4><p>Each mission has one Mission Commander who’s responsible for its success. They periodically report to the Spaceport leader about the mission progress. Everyone’s encouraged to try this role some time.</p><h4>Mission Control HQ</h4><p>While Spaceports have a lot of autonomy, the Mission Control HQ is responsible for overlooking all ongoing or planned missions and deciding on which missions can be launched next. Mission Control HQ consists of all Spaceport Leaders and Society Leaders.</p><h4>Mission Observatory</h4><p>This gives everyone in the company a chance to see the progress of all ongoing missions and provide valuable feedback to the flying Mission Crews. This also gives Mission Control HQ a clear overview of progress across all Spaceports.</p><h4>Societies</h4><p>This is where everyone in a common area of expertise connects. We don’t want Spaceports to be siloed, so we’ll communicate across Spaceports to share experience and knowledge, help each other, and agree on company-wide standards. Currently, we have two main Societies: Product and Engineering.</p><h4>Society Leader</h4><p>Someone who’s responsible for a given Society, making sure our standards are high, and people are happy and growing. This person can help you if there’s an issue in your Spaceport you can’t solve yourself or need to escalate things. Together with Spaceport Leaders, they’re also responsible for hiring.</p><h4>Circles</h4><p>These are smaller, specialized groups focused on different areas of expertise within Societies. Examples are Security, Performance, Product Quality, or Product Design. Their goal is to set and oversee the best practices and keep our standards on the highest possible level. Circles also have dedicated leaders.</p><h4>Circle Leader</h4><p>The leader is responsible for a given area of expertise, and looks for ways to improve and share knowledge across the Spaceports. They ensure that people in their Circle have everything they need for their optimal performance and personal growth.</p><h4>Space Tech Advisory Committee (STAC)</h4><p>A group of nominated people who ensure that what we’re doing works, that we follow certain technical standards, and that newly introduced technologies are used well. The STAC will consist of people who are experts on our products, experts on certain technologies, and architects.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*qS5OUA1suOQu7hl5h36feA.png" /></figure><p>And that’s our SpaceUP vocabulary! Join us next time, when we’ll take a deeper dive into the new organization’s key roles, and explore how all our datanauts work together. See you soon!</p><p><strong>More SpaceUP:</strong></p><ul><li><a href="https://medium.com/ataccama-spaceup/chapter-4-key-roles-in-the-organization-and-their-responsibilities-62a4d89a52a7"><strong>Chapter 4</strong></a></li><li><a href="https://medium.com/ataccama-spaceup/chapter-5-societies-circles-not-yet-another-product-andengineering-matrix-structure-11fdd1b0bb69"><strong>Chapter 5</strong></a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2a28f8d68e42" width="1" height="1" alt=""><hr><p><a href="https://medium.com/ataccama-spaceup/chapter-3-space-up-fundamentals-the-glossary-2a28f8d68e42">Chapter 3 — Space UP fundamentals: The Glossary</a> was originally published in <a href="https://medium.com/ataccama-spaceup">Ataccama SpaceUP</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>