• Share
  • Email
  • Embed
  • Like
  • Save
  • Private Content
Scrum – el efecto en el proceso y la gente
 

Scrum – el efecto en el proceso y la gente

on

  • 1,969 views

Trabajar colaborativamente para lograr equipos altamente productivos es la esencia de SCRUM. ...

Trabajar colaborativamente para lograr equipos altamente productivos es la esencia de SCRUM.

SCRUM es muy indicado para proyectos en entornos complejos, donde los requisitos son cambiantes o poco definidos ¿Te suena esto familiar?

El desarrollo de software se enfrenta totalmente a estos retos y Hubert tiene amplia experiencia ajustando el procesos Scrum a grandes proyectos a partir de pequeños componentes: Gente, producto y proceso.

Durante este Webinar se explicará cómo obtener un mejor rendimiento en el proceso de entrega a través de la aplicación de Scrum.

Statistics

Views

Total Views
1,969
Views on SlideShare
526
Embed Views
1,443

Actions

Likes
1
Downloads
9
Comments
0

3 Embeds 1,443

http://www.sgcampus.com.mx 1281
http://sgcampus.com.mx 161
http://plus.url.google.com 1

Accessibility

Upload Details

Uploaded via as Adobe PDF

Usage Rights

CC Attribution-NonCommercial-NoDerivs LicenseCC Attribution-NonCommercial-NoDerivs LicenseCC Attribution-NonCommercial-NoDerivs License

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

    Scrum – el efecto en el proceso y la gente Scrum – el efecto en el proceso y la gente Presentation Transcript

    • © Cutter Consortium a taste of the agile conference
    • © Cutter Consortium hubert smits senior cutter consultant and member of the agile practice. signatory of the agile manifesto in 2002, scrummaster in 2003 and scrum trainer since 2005.
    • © Cutter Consortium theme scrum at scale: three teams or more
    • © Cutter Consortium scrum shippable - ‘done’ product increment sprint planning meeting •  review product backlog •  select stories for sprint •  task out selected stories •  find owner for each task •  owner estimates task •  commit to 2 weeks of work sprint backlog stories selected, tasked out, estimated by team-members product backlog: ordered features desired by product owner daily sprint sprint review meeting •  demo features to all •  retrospect with team
    • © Cutter Consortium scrum light barely sufficient framework
    • © Cutter Consortium scrum at scale light barely sufficient framework
    • © Cutter Consortium scaling-large
    • © Cutter Consortium scaling-xlarge
    • © Cutter Consortium plantore-plan product 3-4 months refinement vision product needs priorities budget estimates architecture 3-4 vision priorities budget product 3-4 months refinement vision product needs priorities budget estimates architecture
    • © Cutter Consortium refinement: fivelevelsofplanning
    • © Cutter Consortium discussion hubert smits – hsmits@cutter.com