O SlideShare utiliza cookies para otimizar a funcionalidade e o desempenho do site, assim como para apresentar publicidade mais relevante aos nossos usuários. Se você continuar a navegar o site, você aceita o uso de cookies. Leia nosso Contrato do Usuário e nossa Política de Privacidade.
O SlideShare utiliza cookies para otimizar a funcionalidade e o desempenho do site, assim como para apresentar publicidade mais relevante aos nossos usuários. Se você continuar a utilizar o site, você aceita o uso de cookies. Leia nossa Política de Privacidade e nosso Contrato do Usuário para obter mais detalhes.
What is Scrum?• Scrum is
a framework for iterative, incremental development.• Three roles: Product Owner, ScrumMaster and the Team.• Four meetings: Sprint Planning meeting, Daily Scrum, Sprint Review and Retrospective
Scrum is SystemicChange “When the
ﬁve shifts are undertaken simultaneously, as systemic change, the result is sustainable change that is markedly productive for the organization, more congenial to innovation, and more satisfying both for those doing the work and those for whom the work is done.• Ref: http://www.forbes.com/sites/stevedenning/ 2011/05/12/reinventing-management-requires-systemic- change/
So why would youwant to
do it? “An enterprise can use Scrum as a tool to become the best product development and management organization in its market. Scrum will highlight every deﬁciency and impediment that the enterprise has so the enterprise can ﬁx them and change into such an organization.
Top Down• Scrum adoption is
introduced and lead by Senior management ...• Who decide that they want software to be quicker, faster and cheaper• They decide the way to do this is by adopting Agile software development
Top Down• This is done
without understanding the implications of Scrum, and without understanding how this changes:• How people work• How people collaborate• Impact to other business partners
Bottom Up• Scrum adoption is
introduced and lead but the people who do the work ...• Who decide that they want better quality products, delivered at a sustainable pace• They decide the way to do this is by adopting Agile software development
Bottom Up• This is done
without understanding the implications of Scrum, and without understanding how this changes:• Middle and Senior management perceptions• Change to the roles, responsibilities expected of management• Impact on other business partners
Kane’s secret formula1. Top Down
and Bottom Up both at the same time2. Start small and plan for a growing number of Scrum projects3. Target failed or at risk projects ...4. With contained ﬁnancial and political risk
Questions?• I have some questions
for you!• How far up (or down) the organization is Scrum supported within your organization?• Does your management see problems as a learning opportunity?• Is your organization open to changing it’s culture?