{"data":{"id":17901,"title":"Upcoming Roadmap Update","rsi_url":"https:\/\/robertsspaceindustries.com\/comm-link\/transmission\/17901-Upcoming-Roadmap-Update","api_url":"https:\/\/api.star-citizen.wiki\/api\/comm-links\/17901","api_public_url":"https:\/\/api.star-citizen.wiki\/comm-links\/17901","channel":"Undefined","category":"Undefined","series":"None","images":[{"id":22574,"name":"Misc.png","rsi_url":"https:\/\/robertsspaceindustries.com\/media\/vfkyf0zbkq2sur\/source\/Misc.png","alt":"","size":3788,"mime_type":"image\/png","last_modified":"2016-12-14T20:45:47+00:00","api_url":"https:\/\/api.star-citizen.wiki\/api\/comm-link-images\/22574","similar_url":"https:\/\/api.star-citizen.wiki\/api\/comm-link-images\/22574\/similar"},{"id":24592,"name":"StarCitizen.png","rsi_url":"https:\/\/robertsspaceindustries.com\/media\/albozos0cs1a1r\/source\/StarCitizen.png","alt":"","size":6655514,"mime_type":"image\/png","last_modified":"2020-08-17T05:53:00+00:00","api_url":"https:\/\/api.star-citizen.wiki\/api\/comm-link-images\/24592","similar_url":"https:\/\/api.star-citizen.wiki\/api\/comm-link-images\/24592\/similar"},{"id":42314,"name":"Roadmap_Update_2020.mp4","rsi_url":"https:\/\/robertsspaceindustries.com\/media\/je1sny5q5kj2nr\/source\/Roadmap_Update_2020.mp4","alt":"","size":0,"mime_type":"undefined","last_modified":"1970-01-01T00:00:00+00:00","api_url":"https:\/\/api.star-citizen.wiki\/api\/comm-link-images\/42314","similar_url":"https:\/\/api.star-citizen.wiki\/api\/comm-link-images\/42314\/similar"}],"images_count":3,"translations":{"en_EN":"Hi everyone,\nLast time we updated you, we talked about the current roadmap and its limitations, what steps we\u2019re taking to amend that, and shared a work-in-progress shot of our new Roadmap.\nThe new Roadmap has been in active development and we\u2019re still marching towards our end-of-year target. It may seem like a simple task, but an oft-overlooked aspect of building out this Roadmap is the management of such a massive dataset. Building out the front end for a Roadmap isn\u2019t the hardest part \u2013 not even close. The new Roadmap relies on large swaths of data coming in from more than 50 teams, which requires a lot of effort to organize and make presentable for public consumption. In addition, since we\u2019ll be sharing headcount, expertise, and more, this massive dataset will require ongoing and regular maintenance and QC. The key has been in establishing a pipeline\/process so that the new roadmap is sustainable.\nWhat To Expect In December\nSo, what can you expect this December? We plan on delivering a Roadmap that focuses on our core features from our \u201cupstream\u201d teams initially. An \u201cupstream\u201d team is a team that is responsible for a core deliverable (tech\/content\/feature), while \u201cdownstream\u201d teams often won\u2019t have a good idea of their work until the upstream team\u2019s content has been decided and locked in. Downstream teams consist of support teams such as UI, Audio, and other similar teams. The nature of development is obviously that downstream teams have to be reactive to some degree to what upstream teams are working on, which can make it very difficult to accurately map out long-term work. Not only that, but the process works both ways, so often times the downstream evaluations that feed back into upstream planning can alter the upstream team\u2019s timelines.\n\n\nThis video includes real work, real sprints, and real data. This is the format you can expect once we finish gathering data from our teams around the globe to populate the Roadmap for its initial publish. Like we mentioned above, this has been a monumental undertaking for our team, who have been hyper-vigilant in trying to get this right for all of you. Although the work shown in this demo is real, it\u2019s important to note that we haven\u2019t gone through the quarterly planning or go\/no go for everything so the duration, time and scope of the work can change.\nRelease View vs Progress View\nThe new Roadmap is going to have two views that you can cycle through at your leisure: the Progress Tracker (seen in the video) and Release View. Release View is very similar to what you already see on the Public Roadmap that is currently available. This visualization will show you the upcoming releases, with each card being populated by deliverables that we have the highest degree of confidence will make it into that release. That\u2019s why for the immediate release in the quarter ahead, you will see it generously populated. While we intend for this view to show several quarters out, we want to be very clear that due to the nature of priority shifts (which you\u2019ve seen time and time again), visibility beyond one quarter isn\u2019t something you should consider locked. Development is very fluid, and it isn\u2019t until we\u2019ve passed certain milestones that we can gain confidence on delivery times.\nIt\u2019s important for us to set these expectations properly. We\u2019re constantly shuffling our schedules around, whether due to technical accomplishments that bring a feature sooner, or technical hurdles that push things back. It may be the case that we decide that the release view for a card that is several quarters out may be completely blank until we have a high degree of confidence of what deliverables will make it in that time frame. And sometimes, we may find that an unexpected pivot or complication causes us to remove a deliverable we once thought was going to make it. That happens today, but with this new roadmap, you would still see the work in the progress tracking view. This progress tracker view, which is the real highlight of this new roadmap, is what you see in the video above, and again, is our intention to show you all the current work for the quarter for all our teams (starting with upstream teams first), and the subsequent work on tap for these teams in the subsequent quarters down the line.\nProgress and Priorities, Not Promises\nA key goal of ours with the updated Roadmap is to move away from promises of when we think things will arrive, and instead shift the focus to progress and priorities: tracking our current quarter\u2019s progress, what we\u2019re working on, and what our current priorities are for the quarters after. To be entirely candid, we\u2019re fully aware that regardless of caveats or explanations, there will always be folks who see projections as promises. Our new roadmap is not for them; it\u2019s for us to present our progress and priorities, as we said, and show what our teams are working on for those who want to see our development. Content will obviously be more reliable for the current quarter, slightly less so for the quarter right after, and continue to diminish the farther out you go. That is just the nature of development. We don\u2019t always know what we don\u2019t know, and if a team hasn\u2019t started working on a specific piece of content yet, the estimates on velocity and work will not be as accurate. The key is going to be in pulling back the curtain so you know what we know, and to share changes rapidly as our development on deliverables progress every few weeks and sprints.\nThis is a large undertaking for us, and quite frankly, kind of scary. We\u2019re always trying to find better and more innovative ways to present information and especially progress. We\u2019re going to put ourselves out there with this one. We already have ideas for future additions\/improvements and we\u2019ll keep you in the loop along the way.\nTyler Witkin (Zyloh)\nDirector of Community","de_DE":"Hallo zusammen,\nDas letzte Mal, als wir euch auf den neuesten Stand gebracht haben, sprachen wir \u00fcber die aktuelle Roadmap und ihre Grenzen, welche Schritte wir unternehmen, um sie zu \u00e4ndern, und teilten ein in Arbeit befindliches Foto unserer neuen Roadmap.\nDie neue Roadmap ist in aktiver Entwicklung und wir marschieren immer noch auf unser Jahresendziel zu. Es mag wie eine einfache Aufgabe erscheinen, aber ein oft \u00fcbersehener Aspekt bei der Erstellung dieser Roadmap ist die Verwaltung eines solch riesigen Datensatzes. Das Front-End f\u00fcr eine Roadmap zu bauen ist nicht der schwierigste Teil - nicht einmal ann\u00e4hernd. Die neue Roadmap st\u00fctzt sich auf gro\u00dfe Datenmengen, die von mehr als 50 Teams eintreffen, was eine Menge Aufwand erfordert, um sie zu organisieren und f\u00fcr die \u00d6ffentlichkeit vorzeigbar zu machen. Da wir au\u00dferdem die Anzahl der Mitarbeiter, das Fachwissen und mehr teilen werden, wird dieser riesige Datensatz eine st\u00e4ndige und regelm\u00e4\u00dfige Wartung und QC erfordern. Der Schl\u00fcssel lag darin, eine Pipeline\/einen Prozess zu etablieren, damit die neue Roadmap nachhaltig ist.\nWas ist im Dezember zu erwarten?\nAlso, was kannst du diesen Dezember erwarten? Wir planen, eine Roadmap zu erstellen, die sich zun\u00e4chst auf die Kernfunktionen unserer \"Upstream\"-Teams konzentriert. Ein \"Upstream\"-Team ist ein Team, das f\u00fcr eine Kernleistung (Tech\/Inhalt\/Feature) verantwortlich ist, w\u00e4hrend \"Downstream\"-Teams oft erst dann eine gute Vorstellung von ihrer Arbeit haben, wenn der Inhalt des Upstream-Teams feststeht und festgelegt wurde. Downstream-Teams bestehen aus Support-Teams wie UI, Audio und anderen \u00e4hnlichen Teams. Es liegt in der Natur der Entwicklung, dass die Downstream-Teams bis zu einem gewissen Grad darauf reagieren m\u00fcssen, woran die Upstream-Teams arbeiten, was es sehr schwierig machen kann, die langfristige Arbeit genau abzubilden. Und nicht nur das, der Prozess funktioniert in beide Richtungen, so dass die Downstream-Evaluierungen, die in die Planung der Upstream-Teams einflie\u00dfen, oft die Zeitpl\u00e4ne der Upstream-Teams ver\u00e4ndern k\u00f6nnen.\n\nDieses Video beinhaltet echte Arbeit, echte Sprints und echte Daten. Dies ist das Format, das ihr erwarten k\u00f6nnt, sobald wir die Daten von unseren Teams rund um den Globus gesammelt haben, um die Roadmap f\u00fcr ihre erste Ver\u00f6ffentlichung zu f\u00fcllen. Wie wir bereits oben erw\u00e4hnt haben, war dies ein monumentales Unterfangen f\u00fcr unser Team, das hyper-\u00fcberwacht versucht hat, dies f\u00fcr euch alle richtig hinzubekommen. Obwohl die Arbeit, die in dieser Demo gezeigt wird, echt ist, ist es wichtig zu beachten, dass wir nicht die viertelj\u00e4hrliche Planung oder go\/no go f\u00fcr alles durchgegangen sind, so dass sich die Dauer, die Zeit und der Umfang der Arbeit \u00e4ndern kann.\nRelease-Ansicht vs. Fortschrittsansicht\nDie neue Roadmap wird zwei Ansichten haben, die ihr nach Belieben durchfahren k\u00f6nnt: den Progress Tracker (im Video zu sehen) und die Release-Ansicht. Die Release-Ansicht ist sehr \u00e4hnlich zu dem, was ihr bereits auf der \u00f6ffentlichen Roadmap seht, die derzeit verf\u00fcgbar ist. Diese Visualisierung zeigt euch die kommenden Ver\u00f6ffentlichungen, wobei jede Karte mit den Ergebnissen gef\u00fcllt ist, von denen wir das gr\u00f6\u00dfte Vertrauen haben, dass sie es in diese Ver\u00f6ffentlichung schaffen werden. Deshalb werdet ihr f\u00fcr die sofortige Ver\u00f6ffentlichung im kommenden Quartal sehen, dass sie gro\u00dfz\u00fcgig best\u00fcckt sein wird. Auch wenn wir beabsichtigen, dass diese Ansicht mehrere Quartale nach drau\u00dfen zeigt, wollen wir doch sehr deutlich machen, dass aufgrund der Art der Priorit\u00e4tsverschiebungen (die ihr immer wieder gesehen habt), die Sichtbarkeit \u00fcber ein Quartal hinaus nicht als etwas betrachtet werden sollte, das ihr als abgeschlossen betrachten solltet. Die Entwicklung ist sehr fl\u00fcssig, und erst wenn wir bestimmte Meilensteine \u00fcberschritten haben, k\u00f6nnen wir Vertrauen in die Lieferzeiten gewinnen.\nEs ist wichtig f\u00fcr uns, diese Erwartungen richtig zu setzen. Wir mischen st\u00e4ndig unsere Zeitpl\u00e4ne durcheinander, sei es durch technische Errungenschaften, die ein Feature fr\u00fcher bringen, oder durch technische H\u00fcrden, die die Dinge zur\u00fcckwerfen. Es kann sein, dass wir entscheiden, dass die Release-Ansicht f\u00fcr eine Karte, die mehrere Quartale aussteht, komplett leer ist, bis wir ein hohes Ma\u00df an Zuversicht haben, welche Ergebnisse es in diesem Zeitrahmen schaffen werden. Und manchmal stellen wir fest, dass ein unerwarteter Drehpunkt oder eine unerwartete Komplikation dazu f\u00fchrt, dass wir ein Deliverable entfernen, von dem wir einmal dachten, dass wir es schaffen w\u00fcrden. Das passiert heute, aber mit dieser neuen Roadmap w\u00fcrdet ihr die Arbeit immer noch in der Fortschrittsverfolgung sehen. Diese Fortschrittsverfolgungsansicht, die das eigentliche Highlight dieser neuen Roadmap ist, ist das, was ihr in dem Video oben seht, und auch hier wollen wir euch die aktuelle Arbeit f\u00fcr das Quartal f\u00fcr alle unsere Teams zeigen (beginnend mit den Upstream-Teams zuerst) und die nachfolgende Arbeit f\u00fcr diese Teams in den folgenden Quartalen.\nFortschritte und Priorit\u00e4ten, keine Versprechungen\nEin Hauptziel von uns mit der aktualisierten Roadmap ist es, von Versprechungen wegzukommen, wann wir denken, dass die Dinge ankommen werden, und stattdessen den Fokus auf den Fortschritt und die Priorit\u00e4ten zu verlagern: den Fortschritt unseres aktuellen Quartals zu verfolgen, woran wir arbeiten und was unsere aktuellen Priorit\u00e4ten f\u00fcr die Quartale danach sind. Um ganz ehrlich zu sein, wir sind uns v\u00f6llig bewusst, dass es unabh\u00e4ngig von Vorbehalten oder Erkl\u00e4rungen immer Leute geben wird, die Projektionen als Versprechen sehen. Unsere neue Roadmap ist nicht f\u00fcr sie; es liegt an uns, unsere Fortschritte und Priorit\u00e4ten zu pr\u00e4sentieren, wie wir gesagt haben, und zu zeigen, woran unsere Teams arbeiten, f\u00fcr diejenigen, die unsere Entwicklung sehen wollen. Die Inhalte werden nat\u00fcrlich f\u00fcr das laufende Quartal zuverl\u00e4ssiger sein, f\u00fcr das Quartal direkt danach etwas weniger, und sie werden weiter abnehmen, je weiter man hinausgeht. Das ist einfach die Natur der Entwicklung. Wir wissen nicht immer, was wir nicht wissen, und wenn ein Team noch nicht mit der Arbeit an einem bestimmten Inhalt begonnen hat, werden die Sch\u00e4tzungen zur Geschwindigkeit und Arbeit nicht so genau sein. Der Schl\u00fcssel wird darin liegen, den Vorhang zur\u00fcckzuziehen, damit ihr wisst, was wir wissen, und die \u00c4nderungen schnell zu teilen, w\u00e4hrend unsere Entwicklung der Ergebnisse alle paar Wochen und Sprints voranschreitet.\nDas ist ein gro\u00dfes Unterfangen f\u00fcr uns, und ehrlich gesagt, irgendwie be\u00e4ngstigend. Wir versuchen immer, bessere und innovativere Wege zu finden, um Informationen und vor allem Fortschritte zu pr\u00e4sentieren. Damit wollen wir uns selbst auf den Weg bringen. Wir haben bereits Ideen f\u00fcr zuk\u00fcnftige Erg\u00e4nzungen\/Verbesserungen und wir werden euch auf diesem Weg auf dem Laufenden halten.\nTyler Witkin (Zyloh)\nDirektor der Gemeinschaft","zh_CN":"Hi everyone,\nLast time we updated you, we talked about the current roadmap and its limitations, what steps we\u2019re taking to amend that, and shared a work-in-progress shot of our new Roadmap.\nThe new Roadmap has been in active development and we\u2019re still marching towards our end-of-year target. It may seem like a simple task, but an oft-overlooked aspect of building out this Roadmap is the management of such a massive dataset. Building out the front end for a Roadmap isn\u2019t the hardest part \u2013 not even close. The new Roadmap relies on large swaths of data coming in from more than 50 teams, which requires a lot of effort to organize and make presentable for public consumption. In addition, since we\u2019ll be sharing headcount, expertise, and more, this massive dataset will require ongoing and regular maintenance and QC. The key has been in establishing a pipeline\/process so that the new roadmap is sustainable.\nWhat To Expect In December\nSo, what can you expect this December? We plan on delivering a Roadmap that focuses on our core features from our \u201cupstream\u201d teams initially. An \u201cupstream\u201d team is a team that is responsible for a core deliverable (tech\/content\/feature), while \u201cdownstream\u201d teams often won\u2019t have a good idea of their work until the upstream team\u2019s content has been decided and locked in. Downstream teams consist of support teams such as UI, Audio, and other similar teams. The nature of development is obviously that downstream teams have to be reactive to some degree to what upstream teams are working on, which can make it very difficult to accurately map out long-term work. Not only that, but the process works both ways, so often times the downstream evaluations that feed back into upstream planning can alter the upstream team\u2019s timelines.\n\n\nThis video includes real work, real sprints, and real data. This is the format you can expect once we finish gathering data from our teams around the globe to populate the Roadmap for its initial publish. Like we mentioned above, this has been a monumental undertaking for our team, who have been hyper-vigilant in trying to get this right for all of you. Although the work shown in this demo is real, it\u2019s important to note that we haven\u2019t gone through the quarterly planning or go\/no go for everything so the duration, time and scope of the work can change.\nRelease View vs Progress View\nThe new Roadmap is going to have two views that you can cycle through at your leisure: the Progress Tracker (seen in the video) and Release View. Release View is very similar to what you already see on the Public Roadmap that is currently available. This visualization will show you the upcoming releases, with each card being populated by deliverables that we have the highest degree of confidence will make it into that release. That\u2019s why for the immediate release in the quarter ahead, you will see it generously populated. While we intend for this view to show several quarters out, we want to be very clear that due to the nature of priority shifts (which you\u2019ve seen time and time again), visibility beyond one quarter isn\u2019t something you should consider locked. Development is very fluid, and it isn\u2019t until we\u2019ve passed certain milestones that we can gain confidence on delivery times.\nIt\u2019s important for us to set these expectations properly. We\u2019re constantly shuffling our schedules around, whether due to technical accomplishments that bring a feature sooner, or technical hurdles that push things back. It may be the case that we decide that the release view for a card that is several quarters out may be completely blank until we have a high degree of confidence of what deliverables will make it in that time frame. And sometimes, we may find that an unexpected pivot or complication causes us to remove a deliverable we once thought was going to make it. That happens today, but with this new roadmap, you would still see the work in the progress tracking view. This progress tracker view, which is the real highlight of this new roadmap, is what you see in the video above, and again, is our intention to show you all the current work for the quarter for all our teams (starting with upstream teams first), and the subsequent work on tap for these teams in the subsequent quarters down the line.\nProgress and Priorities, Not Promises\nA key goal of ours with the updated Roadmap is to move away from promises of when we think things will arrive, and instead shift the focus to progress and priorities: tracking our current quarter\u2019s progress, what we\u2019re working on, and what our current priorities are for the quarters after. To be entirely candid, we\u2019re fully aware that regardless of caveats or explanations, there will always be folks who see projections as promises. Our new roadmap is not for them; it\u2019s for us to present our progress and priorities, as we said, and show what our teams are working on for those who want to see our development. Content will obviously be more reliable for the current quarter, slightly less so for the quarter right after, and continue to diminish the farther out you go. That is just the nature of development. We don\u2019t always know what we don\u2019t know, and if a team hasn\u2019t started working on a specific piece of content yet, the estimates on velocity and work will not be as accurate. The key is going to be in pulling back the curtain so you know what we know, and to share changes rapidly as our development on deliverables progress every few weeks and sprints.\nThis is a large undertaking for us, and quite frankly, kind of scary. We\u2019re always trying to find better and more innovative ways to present information and especially progress. We\u2019re going to put ourselves out there with this one. We already have ideas for future additions\/improvements and we\u2019ll keep you in the loop along the way.\nTyler Witkin (Zyloh)\nDirector of Community"},"links_count":0,"comment_count":208,"created_at":"2020-11-26T00:00:00+00:00","created_at_human":"5 years ago"},"meta":{"processed_at":"2026-05-07 20:34:34","valid_relations":["images","links"],"prev_id":17899,"next_id":17903}}