



Prepara tus exámenes y mejora tus resultados gracias a la gran cantidad de recursos disponibles en Docsity
Gana puntos ayudando a otros estudiantes o consíguelos activando un Plan Premium
Prepara tus exámenes
Prepara tus exámenes y mejora tus resultados gracias a la gran cantidad de recursos disponibles en Docsity
Prepara tus exámenes con los documentos que comparten otros estudiantes como tú en Docsity
Los mejores documentos en venta realizados por estudiantes que han terminado sus estudios
Estudia con lecciones y exámenes resueltos basados en los programas académicos de las mejores universidades
Responde a preguntas de exámenes reales y pon a prueba tu preparación
Consigue puntos base para descargar
Gana puntos ayudando a otros estudiantes o consíguelos activando un Plan Premium
Comunidad
Pide ayuda a la comunidad y resuelve tus dudas de estudio
Descubre las mejores universidades de tu país según los usuarios de Docsity
Ebooks gratuitos
Descarga nuestras guías gratuitas sobre técnicas de estudio, métodos para controlar la ansiedad y consejos para la tesis preparadas por los tutores de Docsity
caso 1 contienen información relevante para alguien
Tipo: Apuntes
1 / 5
Esta página no es visible en la vista previa
¡No te pierdas las partes importantes!
Atlassian’s 20% Time Experiment I’m happy to announce that we are undertaking a thorough, public “20% time” trial at Atlassian. If you’ve ever wondered how Google’s famed 20% time works in reality, we’ll be your guinea pigs and blogging the results for everyone to see. Why do 20% time? Atlassian has a proud tradition of innovation. We’ve always strived have market leading products, our internal ShipIt days keep improving, we’ve won awards for entrepreneurial innovation and we try to never stop pushing the boundaries in our business. So why are we unhappy? In any startup company, innovation slows as the company grows. Our growing customer base (we just welcomed Customer 10,000) is forcing us to rethink how we innovate in our products, whilst maintaining stability for customers. Wait… so you’re just… copying Google? Well no – we’d love to (we hate re-inventing the wheel!) but it’s a little harder than that. We’d love to start from Google’s model and evolve it but that has proven difficult. You see, while everyone knows about Google’s 20% time and we’ve heard about all the neat products born from it (Google News, GMail etc) – we’ve found it extremely difficult to get any hard facts about how it actually works in practice. We started with a long list of questions:
When can an engineer take his or her time? What restrictions are there about what can and can’t be done in that time? How do technical leads manage their schedules? How does the engineering manager account for the time? Do they track it at all? How do you stop someone’s project if it’s deemed not useful? Who deems it this? Is there a committee? Peer review? How do projects “graduate” from 20% time? How is overall success of the program judged? $$? Customer value? Engineer happiness? Answering these questions and more is what we’re aiming to do in Atlassian’s 20% time experiment. The Trial Here are the outlines of our trial: It will last for 6 months We’ll start with the simplest possible list of rules Rules are allowed to change as we learn We’ll blog everything here We’ll be completely honest – so that others can learn from our experiences
Our hope is that 20% time gives engineers back dedicated slack time – of their own direction – to spend on product innovation, features, plugins, fixes or additions that they think are the most important. We have an absolutely awesome engineering staff. I can’t wait to see what they come up with. What does it mean for customers****? In the short term, this will mean slower or smaller, but more innovative releases. How much slower, smaller and more innovative? We’re not sure – we’ll find out and be honest in communicating it here. (From my back of the envelope calculations, for 7 products we’ve made over 50 releases in the last 12 months.) The long term thinking is that some of the 20% results will filter into the products and outweigh the short term release slow down in terms of customer benefits. What does it mean for other software companies****? Our broadest goal is that all software companies can learn about how the mythical “20% time” actually works in encouraging innovation in a software company. We’ll be blogging regularly here about how things are working. We hope that other technical teams can learn from our investment, experimentation and results. How do we judge success? One of the trickiest questions we’ve looked at internally is “How do we really know if it works?”
Our initial thinking is that to evaluate whether we feel we’ve delivered more customer value given the time investment than we would normally. This customer value could be in terms of new features, improvements to existing features or better internal systems (resulting in say better support answers or quicker ordering). Where do I find out more? Simple – keep reading! We’ll be covering the 20% time experiment from all angles