Scrum Basics 2008
•Transferir como PPTX, PDF•
0 gostou•184 visualizações
Scrum é uma metodologia ágil criada em 2001 que é usada por grandes empresas de tecnologia. Ela funciona em sprints curtos onde equipes self-organizadas selecionam itens de um backlog para entregar valor ao cliente. Cada time conta com um Product Owner, Scrum Master e equipe multifuncional.
Denunciar
Compartilhar
Denunciar
Compartilhar
Recomendados
Introduction to Scrum – Hassan Jaffal
Scrum is the most popular Agile Framework; during this presentation the attendees will understand the value, and an overview of the powerful scrum framework: its roles, its artifacts and its ceremonies
Scrum Bangalore Meetup_5-25 V1.5 2012
This presentation by Jayathirtha Rao on empowering customers and selling agile discusses:
- The presentation is the property of Jayathirtha Rao and may be used for training purposes but not for commercial use without permission.
- Selling agile is really finding what interests customers and seeing if agile can help meet their needs.
- Common concerns about agile like long-term planning, self-organizing teams, and strategic decision making are addressed along with suggestions on how to overcome them.
Scrum day two kinds of scrum
Scrum is simple to explain, yet hard to implement. Often the mechanics are executed without adoption of the underlying principles and values. This happens often where management assumes that Scrum is “just for software development” and that nothing else needs changing. In such situations, Scrum roles, artifacts and events are understood in terms of the prevailing traditional mindset:
- backlog as a specification
- sprint as a small project
- ScrumMaster as project manager
- commitment as a fixed date & scope contract
While such an implementation of Scrum might deliver predictable results and lead to some improvements, it often fails to transform the organisational mindset and culture. Your business might do the wrong things righter instead of delivering better and better products to delight your customers. To achieve a transformation of mindset and culture, an organisation needs to avoid the pitfalls mentioned above and adopt Scrum as a framework that inspires everyone to continually challenge the status quo. One way to achieve this is using Scrum sprints as risk-limiting containers for safe-to-fail experiments. This enables you to deliberately discover the potential of your people's capability and your products' value. Reviews and retrospectives need to be leveraged to drive this continuous improvement process. The talk will increase awareness of these types of Scrum and help you to rather “be agile” instead of just “do agile”—using Scrum to drive that transformation.
Scrum by scrum
Experience Sharing from apply Scrum practice with Scrum Primer translation task
in Agile Tour Bangkok 2012 (Thailand) event.
Scrum ban
Scrumban takes elements of Scrum and Kanban to manage product development workflows. Kanban uses visual boards and work-in-progress limits to maximize flow and control workflow bottlenecks. It was inspired by the Toyota Production System and aims to continuously improve processes. This presentation discusses using Kanban to manage activities outside of Scrum's core development cycles, like backlog management and testing. Kanban complements Scrum by providing visibility and control over the entire value stream. The speaker recommends Scrumban for long development cycles, heavy R&D, and support/helpdesk teams.
Scrum Bangalore 18th Meetup - October 15, 2016 - Elasticity of Kanban - Saika...
The document discusses scaling Kanban across teams and organizations. It describes expanding Kanban in three dimensions: width, height, and depth. Width involves extending the workflow upstream and downstream. Height involves linking different levels of work from portfolio to personal tasks. Depth involves visualizing and managing interdependent services across shared resources. The document provides examples and recommendations for coordinating Kanban at scale, including common metrics, managing work in progress limits, and benefits of scaling Kanban such as increased flow and throughput.
Scrum based methodology for distributed software development
This presentation is in Farsi
Presented by Me in 24th May 2016 in AmirKabir University of Technology
Navid Sedighpour
--------------------------------------------------------------------------
ارائه به زبان فارسی است
چهارم خرداد سال 1395 در دانشگاه صنعتی امیرکبیر
نوید صدیق پور
Recomendados
Introduction to Scrum – Hassan Jaffal
Scrum is the most popular Agile Framework; during this presentation the attendees will understand the value, and an overview of the powerful scrum framework: its roles, its artifacts and its ceremonies
Scrum Bangalore Meetup_5-25 V1.5 2012
This presentation by Jayathirtha Rao on empowering customers and selling agile discusses:
- The presentation is the property of Jayathirtha Rao and may be used for training purposes but not for commercial use without permission.
- Selling agile is really finding what interests customers and seeing if agile can help meet their needs.
- Common concerns about agile like long-term planning, self-organizing teams, and strategic decision making are addressed along with suggestions on how to overcome them.
Scrum day two kinds of scrum
Scrum is simple to explain, yet hard to implement. Often the mechanics are executed without adoption of the underlying principles and values. This happens often where management assumes that Scrum is “just for software development” and that nothing else needs changing. In such situations, Scrum roles, artifacts and events are understood in terms of the prevailing traditional mindset:
- backlog as a specification
- sprint as a small project
- ScrumMaster as project manager
- commitment as a fixed date & scope contract
While such an implementation of Scrum might deliver predictable results and lead to some improvements, it often fails to transform the organisational mindset and culture. Your business might do the wrong things righter instead of delivering better and better products to delight your customers. To achieve a transformation of mindset and culture, an organisation needs to avoid the pitfalls mentioned above and adopt Scrum as a framework that inspires everyone to continually challenge the status quo. One way to achieve this is using Scrum sprints as risk-limiting containers for safe-to-fail experiments. This enables you to deliberately discover the potential of your people's capability and your products' value. Reviews and retrospectives need to be leveraged to drive this continuous improvement process. The talk will increase awareness of these types of Scrum and help you to rather “be agile” instead of just “do agile”—using Scrum to drive that transformation.
Scrum by scrum
Experience Sharing from apply Scrum practice with Scrum Primer translation task
in Agile Tour Bangkok 2012 (Thailand) event.
Scrum ban
Scrumban takes elements of Scrum and Kanban to manage product development workflows. Kanban uses visual boards and work-in-progress limits to maximize flow and control workflow bottlenecks. It was inspired by the Toyota Production System and aims to continuously improve processes. This presentation discusses using Kanban to manage activities outside of Scrum's core development cycles, like backlog management and testing. Kanban complements Scrum by providing visibility and control over the entire value stream. The speaker recommends Scrumban for long development cycles, heavy R&D, and support/helpdesk teams.
Scrum Bangalore 18th Meetup - October 15, 2016 - Elasticity of Kanban - Saika...
The document discusses scaling Kanban across teams and organizations. It describes expanding Kanban in three dimensions: width, height, and depth. Width involves extending the workflow upstream and downstream. Height involves linking different levels of work from portfolio to personal tasks. Depth involves visualizing and managing interdependent services across shared resources. The document provides examples and recommendations for coordinating Kanban at scale, including common metrics, managing work in progress limits, and benefits of scaling Kanban such as increased flow and throughput.
Scrum based methodology for distributed software development
This presentation is in Farsi
Presented by Me in 24th May 2016 in AmirKabir University of Technology
Navid Sedighpour
--------------------------------------------------------------------------
ارائه به زبان فارسی است
چهارم خرداد سال 1395 در دانشگاه صنعتی امیرکبیر
نوید صدیق پور
ScrumDesk
ScrumDesk is an agile project management tool that allows users to manage projects, stories, and tasks using cards on customizable boards. It offers features like backlog management, sprint planning, prioritization, reporting, timesheets, and integrations with communication tools to help teams self-organize and track their progress. The tool is accessible from their website at www.scrumdesk.com.
Scrum Board
This document outlines elements of a Scrum process including a product backlog, sprint backlog, task board to track items as to do, in progress, and done, as well as elements like a backlog refinement meeting, impediments log, and sprint burndown chart to track progress toward completing items in the sprint. The overall product vision drives the selection of items in the backlog.
Scrum Bangalore 18th Meetup - October 15, 2016 - Agile Architecture - Deepak ...
The document discusses agile architecture and how architecture can support agile development. It defines agile architecture as one that allows quick replacement of details and is easy to verify. An agile architecture enables the principles of the Agile Manifesto by allowing for quick change and being verifiable at any point. Traditional architecture focuses on rules and limitations, while agile architecture is needed to support rapid development, continuous delivery of value, and managing change and complexity. The document outlines practices of agile architecture including having architecture as part of the scrum team and modeling and documenting in an agile fashion. It also discusses roles like the agile architect and characteristics like understanding stakeholders and having a big picture view.
Scrum Cafe
Este documento presenta las pautas para una reunión de "Scrum Café" enfocada en discutir Scrum de una manera informal y colaborativa. Propone crear un ambiente hospitalario, explorar preguntas pertinentes, escuchar diferentes perspectivas, enfocarse en lo importante, contribuir y discutir ideas respetuosamente, y divertirse conversando sobre Scrum. También incluye preguntas de discusión sobre Scrum, sus valores y principios, herramientas, relación con otras disciplinas, y futuro.
Individuals and interactions over processes and tools
This document discusses how processes and activities fit into agile software development using Scrum. It describes the typical activities involved in system and software development like defining requirements, design, implementation, integration and testing. It argues that while processes are still needed, the focus should be on individuals and interactions over processes. Stories represent requirements and processes need to be satisfied when stories are delivered, but the level of formality is determined by risk. Technical debt can occur if all processes aren't followed for a story.
SCRUM Core Concepts
The document outlines the core concepts of the Scrum framework, including the roles of the Product Owner, ScrumMaster, and Development Team. It also describes the Scrum activities and artifacts like the Product Backlog, Sprints, Sprint Planning, Daily Scrums, Sprint Reviews, and Sprint Retrospectives. The Product Owner is responsible for the product vision and prioritizing the backlog. The ScrumMaster helps the team use Scrum and removes impediments. The Development Team works in sprints to complete items from the backlog.
Scrum Days Poland 2016 - The future present of Scrum (by Gunther Verheyen)
Scrum is about to turn 21. Scrum became a key tool for teams and organizations to deal with the increased criticality of software. Depending on the source, 60-90% of all Agile teams worldwide say they employ Scrum.
Are we Done yet with Scrum? No more challenges? Time to move on?
In this 18 minutes keynote Gunther says we are not Done with Scrum yet. Gunther shows that the key to the future of Scrum is creating Done Increments of product, where “Done” actually means “releasable in production.” It might take another two decades to actually get there.
PermaMatrix is cheaper than dirt!
This is a brief comparison of PermaMatrix vs. topsoil, mulch and compost. By hydraulically applying this organic biotic soil amendment containing Biochar, you will not only cut costs, but also cut pollution and create a sustainable environment for plants to thrive.
Scrum Clock 2 week
This document discusses a 2-week sprint goal definition and definition of done for a Scrum project. It lists the days of the week (WE, TH, TU, FR, MO, TU, TH, MO, FR) and mentions a sprint goal and definition of done. The document was created by Nigel Thurlow and last updated on March 10, 2015.
Scrum bangalore 12 march 7 2015 - john barrat - scaling scrum it is the peo...
This document discusses scaling Scrum across distributed teams. It suggests that what makes a good team member and high performing agile team is more important than physical location. Distributed teams can be used effectively when the members in different locations are energized, focused and work together towards shared values, as demonstrated by one company's experience with a distributed team across Australia and India.
Scrum_BLR 9th meet up 28-Jun-2014 - Lies, Damn Lies... Estimates - Bhavin Kamani
Estimates, especially for software projects, are highly inaccurate due to various challenges and laws of nature. It is difficult to provide confident estimates for tasks as simple as a person's age or as complex as the number of bugs in a project. Parkinson's Law and the Student Syndrome mean that people will naturally procrastinate and not finish work on time if given too much time. Estimates also become less accurate the more granular they are due to exponential aggregation error. Instead of relying on estimates, it is better to measure progress using techniques like story points, cycle time, and cumulative flow diagrams, and to break work down into smaller chunks with clear requirements.
Scrum Clinic Amsterdam 2010
This document summarizes an experimental Scrum Clinic event held in Amsterdam in 2010 to provide a forum for focused conversations and coaching on Scrum and agile topics. Key aspects of the event included:
1) The clinic was organized using agile principles and had facilitators guide discussion in 10 breakout groups on topics identified by participants.
2) Detailed preparation was required including defining roles, prioritizing discussion topics, and setting guidelines for productive conversations.
3) Feedback was positive and lessons included the benefit of mindful preparation, effective facilitation in pairs, and incorporating multiple learning loops like group discussions, documentation, and a retrospective.
Scrum methodology Infographic
Another one-pager presenting the mechanics of the scrum methodology on a small (but quite complete) infographic
Scrum Certified Trainer
This document appears to be a record containing identifying information such as a name, date, and reference code. It lists Kuljeet Singh Sarna's name and dates from March 04, 2015 to March 03, 2016 along with the reference code SCT - 20150172.
Scrum_BLR 9th meet up 28-Jun-2014 - Kanban and Scrum - Anand Gothe
Kanban and Scrum provide different approaches for workflow management. Kanban focuses on visualizing and limiting work in progress to measure lead times, while Scrum prescribes specific roles, iterations, teams, and processes. However, both use transparency and limiting work in progress to drive improvements. Many Scrum practices like standups, reviews, and retrospectives can still be useful when combining Kanban and Scrum.
Workshop Desenvolvimento Ágil
Material de apoio do Workshop de Desenvolvimento Ágil oferecido para estudantes universitário participantes do Ideias Já!, primeira competição universitária de ideias realizado pela Startup House em novembro de 2012.
Fiveday - Falando de Scrum (conceitos e práticas utilizando métodos Ágeis)
O documento fornece uma visão geral de Scrum em uma apresentação. Resume os principais pontos como: o que é Scrum, as pessoas envolvidas (Product Owner, Scrum Master e equipe), planejamento com Scrum, ferramentas de Scrum e um caso de sucesso da Fivecom usando Scrum.
Gestão de Produtos com Scrum e algo mais...
O documento discute a gestão de produtos com SCRUM, descrevendo os princípios e práticas ágeis como trabalhar de forma iterativa e incremental, priorizar o valor de negócio e o feedback do cliente, e entregar valor constantemente por meio de incrementos potencialmente entregáveis do produto. O SCRUM inspirou o movimento Lean Startup ao possibilitar rápidas iterações de desenvolvimento e aprendizado com feedback do cliente.
Agile Business Owner: O Papel Mais Crítico na Agilidade de Negócios
1) O documento apresenta Luiz Parzianello, um pioneiro da agilidade no Brasil e fundador da Agile Business Owner Academy, que fornece educação e certificação para proprietários de negócios ágeis.
2) A agilidade de negócios visa desenvolver novas capacidades organizacionais para responder rapidamente às necessidades dos clientes, adaptar-se às mudanças do mercado e acelerar o crescimento.
3) O papel do proprietário de negócios ágil é liderar a estratégia, execução e iniciat
Mais conteúdo relacionado
Destaque
ScrumDesk
ScrumDesk is an agile project management tool that allows users to manage projects, stories, and tasks using cards on customizable boards. It offers features like backlog management, sprint planning, prioritization, reporting, timesheets, and integrations with communication tools to help teams self-organize and track their progress. The tool is accessible from their website at www.scrumdesk.com.
Scrum Board
This document outlines elements of a Scrum process including a product backlog, sprint backlog, task board to track items as to do, in progress, and done, as well as elements like a backlog refinement meeting, impediments log, and sprint burndown chart to track progress toward completing items in the sprint. The overall product vision drives the selection of items in the backlog.
Scrum Bangalore 18th Meetup - October 15, 2016 - Agile Architecture - Deepak ...
The document discusses agile architecture and how architecture can support agile development. It defines agile architecture as one that allows quick replacement of details and is easy to verify. An agile architecture enables the principles of the Agile Manifesto by allowing for quick change and being verifiable at any point. Traditional architecture focuses on rules and limitations, while agile architecture is needed to support rapid development, continuous delivery of value, and managing change and complexity. The document outlines practices of agile architecture including having architecture as part of the scrum team and modeling and documenting in an agile fashion. It also discusses roles like the agile architect and characteristics like understanding stakeholders and having a big picture view.
Scrum Cafe
Este documento presenta las pautas para una reunión de "Scrum Café" enfocada en discutir Scrum de una manera informal y colaborativa. Propone crear un ambiente hospitalario, explorar preguntas pertinentes, escuchar diferentes perspectivas, enfocarse en lo importante, contribuir y discutir ideas respetuosamente, y divertirse conversando sobre Scrum. También incluye preguntas de discusión sobre Scrum, sus valores y principios, herramientas, relación con otras disciplinas, y futuro.
Individuals and interactions over processes and tools
This document discusses how processes and activities fit into agile software development using Scrum. It describes the typical activities involved in system and software development like defining requirements, design, implementation, integration and testing. It argues that while processes are still needed, the focus should be on individuals and interactions over processes. Stories represent requirements and processes need to be satisfied when stories are delivered, but the level of formality is determined by risk. Technical debt can occur if all processes aren't followed for a story.
SCRUM Core Concepts
The document outlines the core concepts of the Scrum framework, including the roles of the Product Owner, ScrumMaster, and Development Team. It also describes the Scrum activities and artifacts like the Product Backlog, Sprints, Sprint Planning, Daily Scrums, Sprint Reviews, and Sprint Retrospectives. The Product Owner is responsible for the product vision and prioritizing the backlog. The ScrumMaster helps the team use Scrum and removes impediments. The Development Team works in sprints to complete items from the backlog.
Scrum Days Poland 2016 - The future present of Scrum (by Gunther Verheyen)
Scrum is about to turn 21. Scrum became a key tool for teams and organizations to deal with the increased criticality of software. Depending on the source, 60-90% of all Agile teams worldwide say they employ Scrum.
Are we Done yet with Scrum? No more challenges? Time to move on?
In this 18 minutes keynote Gunther says we are not Done with Scrum yet. Gunther shows that the key to the future of Scrum is creating Done Increments of product, where “Done” actually means “releasable in production.” It might take another two decades to actually get there.
PermaMatrix is cheaper than dirt!
This is a brief comparison of PermaMatrix vs. topsoil, mulch and compost. By hydraulically applying this organic biotic soil amendment containing Biochar, you will not only cut costs, but also cut pollution and create a sustainable environment for plants to thrive.
Scrum Clock 2 week
This document discusses a 2-week sprint goal definition and definition of done for a Scrum project. It lists the days of the week (WE, TH, TU, FR, MO, TU, TH, MO, FR) and mentions a sprint goal and definition of done. The document was created by Nigel Thurlow and last updated on March 10, 2015.
Scrum bangalore 12 march 7 2015 - john barrat - scaling scrum it is the peo...
This document discusses scaling Scrum across distributed teams. It suggests that what makes a good team member and high performing agile team is more important than physical location. Distributed teams can be used effectively when the members in different locations are energized, focused and work together towards shared values, as demonstrated by one company's experience with a distributed team across Australia and India.
Scrum_BLR 9th meet up 28-Jun-2014 - Lies, Damn Lies... Estimates - Bhavin Kamani
Estimates, especially for software projects, are highly inaccurate due to various challenges and laws of nature. It is difficult to provide confident estimates for tasks as simple as a person's age or as complex as the number of bugs in a project. Parkinson's Law and the Student Syndrome mean that people will naturally procrastinate and not finish work on time if given too much time. Estimates also become less accurate the more granular they are due to exponential aggregation error. Instead of relying on estimates, it is better to measure progress using techniques like story points, cycle time, and cumulative flow diagrams, and to break work down into smaller chunks with clear requirements.
Scrum Clinic Amsterdam 2010
This document summarizes an experimental Scrum Clinic event held in Amsterdam in 2010 to provide a forum for focused conversations and coaching on Scrum and agile topics. Key aspects of the event included:
1) The clinic was organized using agile principles and had facilitators guide discussion in 10 breakout groups on topics identified by participants.
2) Detailed preparation was required including defining roles, prioritizing discussion topics, and setting guidelines for productive conversations.
3) Feedback was positive and lessons included the benefit of mindful preparation, effective facilitation in pairs, and incorporating multiple learning loops like group discussions, documentation, and a retrospective.
Scrum methodology Infographic
Another one-pager presenting the mechanics of the scrum methodology on a small (but quite complete) infographic
Scrum Certified Trainer
This document appears to be a record containing identifying information such as a name, date, and reference code. It lists Kuljeet Singh Sarna's name and dates from March 04, 2015 to March 03, 2016 along with the reference code SCT - 20150172.
Scrum_BLR 9th meet up 28-Jun-2014 - Kanban and Scrum - Anand Gothe
Kanban and Scrum provide different approaches for workflow management. Kanban focuses on visualizing and limiting work in progress to measure lead times, while Scrum prescribes specific roles, iterations, teams, and processes. However, both use transparency and limiting work in progress to drive improvements. Many Scrum practices like standups, reviews, and retrospectives can still be useful when combining Kanban and Scrum.
Destaque (18)
Scrum Bangalore 18th Meetup - October 15, 2016 - Agile Architecture - Deepak ...
Scrum Bangalore 18th Meetup - October 15, 2016 - Agile Architecture - Deepak ...
Individuals and interactions over processes and tools
Individuals and interactions over processes and tools
Scrum Days Poland 2016 - The future present of Scrum (by Gunther Verheyen)
Scrum Days Poland 2016 - The future present of Scrum (by Gunther Verheyen)
Scrum bangalore 12 march 7 2015 - john barrat - scaling scrum it is the peo...
Scrum bangalore 12 march 7 2015 - john barrat - scaling scrum it is the peo...
Scrum_BLR 9th meet up 28-Jun-2014 - Lies, Damn Lies... Estimates - Bhavin Kamani
Scrum_BLR 9th meet up 28-Jun-2014 - Lies, Damn Lies... Estimates - Bhavin Kamani
Scrum Developer Certified Credential (Nabil Kawwa)
Scrum Developer Certified Credential (Nabil Kawwa)
Scrum_BLR 9th meet up 28-Jun-2014 - Kanban and Scrum - Anand Gothe
Scrum_BLR 9th meet up 28-Jun-2014 - Kanban and Scrum - Anand Gothe
Semelhante a Scrum Basics 2008
Workshop Desenvolvimento Ágil
Material de apoio do Workshop de Desenvolvimento Ágil oferecido para estudantes universitário participantes do Ideias Já!, primeira competição universitária de ideias realizado pela Startup House em novembro de 2012.
Fiveday - Falando de Scrum (conceitos e práticas utilizando métodos Ágeis)
O documento fornece uma visão geral de Scrum em uma apresentação. Resume os principais pontos como: o que é Scrum, as pessoas envolvidas (Product Owner, Scrum Master e equipe), planejamento com Scrum, ferramentas de Scrum e um caso de sucesso da Fivecom usando Scrum.
Gestão de Produtos com Scrum e algo mais...
O documento discute a gestão de produtos com SCRUM, descrevendo os princípios e práticas ágeis como trabalhar de forma iterativa e incremental, priorizar o valor de negócio e o feedback do cliente, e entregar valor constantemente por meio de incrementos potencialmente entregáveis do produto. O SCRUM inspirou o movimento Lean Startup ao possibilitar rápidas iterações de desenvolvimento e aprendizado com feedback do cliente.
Agile Business Owner: O Papel Mais Crítico na Agilidade de Negócios
1) O documento apresenta Luiz Parzianello, um pioneiro da agilidade no Brasil e fundador da Agile Business Owner Academy, que fornece educação e certificação para proprietários de negócios ágeis.
2) A agilidade de negócios visa desenvolver novas capacidades organizacionais para responder rapidamente às necessidades dos clientes, adaptar-se às mudanças do mercado e acelerar o crescimento.
3) O papel do proprietário de negócios ágil é liderar a estratégia, execução e iniciat
Pré-Jogo / Inception - Descobrindo Produtos Viáveis
Ao iniciar o desenvolvimento de um projeto ou produto, queremos algumas coisas: saber onde chegar, ter alinhamento, entender que problema estamos resolvendo, como sabemos que estamos no caminho, como entender pontos de parada para tornar a jornada mais consciente, e por aí vai.
Um exercício de pré-jogo pode ajudar a entender esse caminho, e entender o que pode ser feito para alcançar os resultados que se esperam.
Visão de produto, útil para apontar todos para o mesmo lugar.
Identificar para quem estamos fazendo este produto / projeto, e expectativas destas pessoas.
Identificar o que pode ser feito para resolver os problemas que estas pessoas que identificamos possuem.
Saber o que é mais importante em alguma estratégia de classificação e qualificação.
Priorizar para gerar valor o mais cedo possível.
Inspecionar e adaptar sempre que necessário, e validar o valor sendo gerado a cada iteração de trabalho.
Queremos o resultado, mas queremos mais ainda, valorizar a jornada. :)
Lean Inception custo ou desperdício? Como engajar participantes?
O documento apresenta informações sobre Mayra Souza e Gabriela Corrêa, duas profissionais que atuam como Agile Coaches e facilitadoras. Detalha suas formações acadêmicas e experiências profissionais atuando em transformação organizacional, treinamentos, reengenharia de processos e gestão de produtos.
Workshop Inception Enxuta em Alphaville na Catho
Este documento resume um workshop sobre Inception Enxuta. Ele descreve as atividades realizadas durante o workshop, incluindo definição de MVP, planejamento da semana, identificação de personas e funcionalidades, nivelamento de funcionalidades, trade-offs, jornada do usuário e sequenciamento de funcionalidades em MVPs. O objetivo é praticar uma abordagem enxuta para planejar o início de um projeto de forma colaborativa.
Pra que serve um agile coach
O documento discute os conceitos e práticas de Agile e o papel de um Agile Coach. Ele explica como o Agile Coach ajuda times e empresas a melhorar a produtividade e performance através de técnicas como planejamento ágil, formação de times, mentoria, capacitação e análise de métricas. O Agile Coach também apoia a implementação de Agile em escala na empresa.
Agilidade além do scrum
Palestra apresentada na undb em 07/03/2017 com o objetivo de quebrar a visão de agilidade atrelada apenas ao Scrum, demonstrando a mesma de forma mais ampla
Scrum
Este documento fornece um resumo conciso sobre Scrum e suas principais características:
[1] Scrum é um framework ágil para gestão e desenvolvimento de projetos que enfatiza a colaboração, adaptabilidade e entrega contínua de valor ao cliente.
[2] Nos projetos Scrum, as equipes autorganizáveis ("times Scrum") estimam o trabalho, planejam sprints curtas e entregam software funcionando frequentemente para obter feedback do cliente.
[3] Os principais papéis no Scrum são o
Agile
O documento fornece um resumo sobre a abordagem ágil para desenvolvimento de software. Ele descreve os principais problemas com o desenvolvimento tradicional de software, como requisitos incompletos e mudanças frequentes, e introduz os princípios ágeis de entrega contínua e colaboração próxima com os clientes. Também resume alguns métodos ágeis populares como Scrum e Kanban, destacando práticas como sprints curtas e limitação de trabalho em andamento.
Workshop Inception Enxuta
Este documento resume um workshop sobre Inception Enxuta. Ele apresenta Mayra Souza e Paulo Caroli, os facilitadores, e descreve as atividades planejadas para a inception, incluindo definir a visão do produto, objetivos, personas, funcionalidades, jornada do usuário, sequenciamento em MVPs e canvas MVP. O workshop visa alinhar a equipe e entender coletivamente o escopo inicial do produto.
Workshop Inception Enxuta em Brasília
Facilitação Mayra Souza e Yoris Linhares
Por que uma Inception?
Projetos ágeis são conduzidos através de entregas rápidas e frequentes, focando nas entregas de valor de acordo com objetivos de negócios e as necessidades dos usuários promovendo a liberação incremental de software: o MVP. O produto viável mínimo, em Inglês Minimum Viable Product (MVP), é a versão mais simples de um produto que pode ser disponibilizada para o negócio.
A técnica da Inception DiretoAoPonto foca no entendimento de valor do negócio e necessidade do usuário para sequenciar o MVP, no produto mínimo, na validação de pedaços menores, bem menos elaborados do que uma versão final, mas viável para verificar se o direcionamento está correto. Ao final da Inception terá a equipe muito bem alinhada e pronta para desenvolver o MVP.
Compartilhe com o grupo Direto ao Ponto sua experiência com Inception Enxuta: https://www.facebook.com/groups/1523314637977042/?fref=ts
Do Backlog ao Produto - Scrum Gathering Rio 2018
Foi um longo caminho desde o manifesto ágil. Hoje, o Scrum é o framework mais adotado. O papel do PO foi concebido para um time ágil de 3 a 10 pessoas. Na época, o principal desafio era entregar software.
Hoje, as iniciativas de produto frequentemente exigem o trabalho coordenado de diversos times. Muitas vezes, chega-se a centenas de pessoas em uma iniciativa. Por outro lado, entregar software não é mais suficiente. É preciso criar impacto real na vida dos clientes e no negócio da sua empresa.
Veja algumas reflexões sobre o que é ser um PO em 2018.
Scrum
Este documento fornece uma introdução ao framework Scrum, descrevendo suas origens, pilares, papéis, artefatos e cerimônias. O documento também discute desafios comuns na adoção do Scrum e como lidar com eles.
Workshop Inception Enxuta em Joinville na ContaAzul
Facilitação Mayra Souza e Marco Antonio Silva
Por que uma Inception?
Projetos ágeis são conduzidos através de entregas rápidas e frequentes, focando nas entregas de valor de acordo com objetivos de negócios e as necessidades dos usuários promovendo a liberação incremental de software: o MVP. O produto viável mínimo, em Inglês Minimum Viable Product (MVP), é a versão mais simples de um produto que pode ser disponibilizada para o negócio.
A técnica da Inception DiretoAoPonto foca no entendimento de valor do negócio e necessidade do usuário para sequenciar o MVP, no produto mínimo, na validação de pedaços menores, bem menos elaborados do que uma versão final, mas viável para verificar se o direcionamento está correto. Ao final da Inception terá a equipe muito bem alinhada e pronta para desenvolver o MVP.
Compartilhe com o grupo Direto ao Ponto sua experiência com Inception Enxuta: https://www.facebook.com/groups/1523314637977042/?fref=ts
AÇÃO Criando ambientes colaborativos & criativos: https://www.facebook.com/acaocriandoambientes/
State of Product Ownership - Scrum Day BR 2018
Foi um longo caminho desde o manifesto ágil. Hoje, o Scrum é o framework mais adotado. O papel do PO foi concebido para um time ágil de 3 a 10 pessoas. Na época, o principal desafio era entregar software.
Hoje, as iniciativas de produto frequentemente exigem o trabalho coordenado de diversos times. Muitas vezes, chega-se a centenas de pessoas em uma iniciativa.
Por outro lado, entregar software não é mais suficiente. É preciso criar impacto real na vida dos clientes e no negócio da sua empresa.
O papel do product owner varia dependendo de cada um desses contextos. Veja algumas reflexões sobre o que é um PO em 2018.
Mini curso de testes ágeis
Este documento fornece informações sobre um mini-curso sobre teste ágil, incluindo contatos do instrutor e da empresa organizadora, Qualister. O curso abordará como o teste ágil funciona na prática e os princípios do desenvolvimento ágil.
Scrum agil
O documento discute a aplicação do framework Scrum e da metodologia Kanban usando a ferramenta Trello para gerenciar projetos. Ele explica brevemente o que são Scrum, Kanban e Trello e como eles podem ser usados juntos para melhorar a produtividade de equipes.
Gestão de Produtos de Software - RanchoDev
Gestão de Produtos: como aumentar as chances de sucesso do seu software? Palestra do #RanchoDev (02/Set/2016)
Semelhante a Scrum Basics 2008 (20)
Fiveday - Falando de Scrum (conceitos e práticas utilizando métodos Ágeis)
Fiveday - Falando de Scrum (conceitos e práticas utilizando métodos Ágeis)
Agile Business Owner: O Papel Mais Crítico na Agilidade de Negócios
Agile Business Owner: O Papel Mais Crítico na Agilidade de Negócios
Pré-Jogo / Inception - Descobrindo Produtos Viáveis
Pré-Jogo / Inception - Descobrindo Produtos Viáveis
Lean Inception custo ou desperdício? Como engajar participantes?
Lean Inception custo ou desperdício? Como engajar participantes?
Workshop Inception Enxuta em Joinville na ContaAzul
Workshop Inception Enxuta em Joinville na ContaAzul
Scrum Basics 2008
- 1. SCRUM
- 2. DE ONDE VEIO ISSO? AgileAlliance em 2001 Empresas que já usam: Microsoft Yahoo Google EletronicArts Phillips Siemens Nokia E muitas outras
- 3. E COMO FUNCIONA? ? ? ? ? ? ?
- 4. Lista de características, funcionalidades mais óbvias Priorizado e estimado Gerada em conjunto com o cliente! Sempre visível Mutável PRODUCT BACKLOG
- 5. Lista de características, funcionalidades mais óbvias Priorizado e estimado Gerada em conjunto com o cliente! Sempre visível Mutável PRODUCT BACKLOG
- 6. Lista de características, funcionalidades mais óbvias Priorizado e estimado Gerada em conjunto com o cliente! Sempre visível Mutável PRODUCT BACKLOG
- 7. Lista de características, funcionalidades mais óbvias Priorizado e estimado Gerada em conjunto com o cliente! Sempre visível Mutável PRODUCT BACKLOG
- 8. Lista de características, funcionalidades mais óbvias Priorizado e estimado Gerada em conjunto com o cliente! Sempre visível Mutável PRODUCT BACKLOG
- 9. Sprint = ciclo A equipe decide Considerar prioridades SPRINT BACKLOG
- 10. Sprint = ciclo A equipe decide Considerar prioridades SPRINT BACKLOG
- 12. Responsável pelo ROI
- 14. Auto-organizável
- 15. ComprometidosProductOwner ScrumTeam ScrumMaster
- 17. Responsável por disseminar as práticas e valores
- 18. Lida com o cliente
- 20. Facilitador
- 21. Responsável pela qualidade e produtividadeProductOwner ScrumTeam ScrumMaster
- 22. A ITERAÇÃO Sprintplanning meeting Dailyscrum Sprintreview meeting
- 24. Pró-Atividade Auto-organização (trabalho em equipe) Transparência Comprometimento Simplicidade Done is done! ALGUNS VALORES
- 25. Pró-Atividade Auto-organização (trabalho em equipe) Transparência Comprometimento Simplicidade Done is done! ALGUNS VALORES
- 26. Pró-Atividade Auto-organização (trabalho em equipe) Transparência Comprometimento Simplicidade Done is done! ALGUNS VALORES
- 27. Pró-Atividade Auto-organização (trabalho em equipe) Transparência Comprometimento Simplicidade Done is done! ALGUNS VALORES
- 28. Pró-Atividade Auto-organização (trabalho em equipe) Transparência Comprometimento Simplicidade Done is done! ALGUNS VALORES
- 29. RECAPTULANDO
- 30. PERGUNTAS?