Scribd Logo
Upload

Welcome to Scribd!

  • Sprint 13 Retro

    Uploaded by

    Anton Spektorov
    5 views1 page
    The team discussed areas to improve for the next sprint including starting to allow more time for deployments in planning, stopping scheduling placeholder meetings mid-sprint that not everyone can attend, and continuing to streamline the engagement of business stakeholders in deployment planning and the kanban boards. They also considered starting internal walk-throughs before business reviews, stopping long term scheduling challenges when involving multiple departments, and continuing asynchronous remediation practices. Finally, the team discussed starting to use more production data for business reviews and investigating ways to speed up demos and performance.

    Original Description:

    Copyright

    © © All Rights Reserved

    Available Formats

    PDF, TXT or read online from Scribd

    Did you find this document useful?

    Is this content inappropriate?

    Report this Document
    The team discussed areas to improve for the next sprint including starting to allow more time for deployments in planning, stopping scheduling placeholder meetings mid-sprint that not everyone can attend, and continuing to streamline the engagement of business stakeholders in deployment planning and the kanban boards. They also considered starting internal walk-throughs before business reviews, stopping long term scheduling challenges when involving multiple departments, and continuing asynchronous remediation practices. Finally, the team discussed starting to use more production data for business reviews and investigating ways to speed up demos and performance.

    Copyright:

    © All Rights Reserved
    Download as PDF, TXT or read online from Scribd
    Flag for inappropriate content
    Download as pdf or txt
    5 views1 page

    Sprint 13 Retro

    Uploaded by

    Anton Spektorov
    The team discussed areas to improve for the next sprint including starting to allow more time for deployments in planning, stopping scheduling placeholder meetings mid-sprint that not everyone can attend, and continuing to streamline the engagement of business stakeholders in deployment planning and the kanban boards. They also considered starting internal walk-throughs before business reviews, stopping long term scheduling challenges when involving multiple departments, and continuing asynchronous remediation practices. Finally, the team discussed starting to use more production data for business reviews and investigating ways to speed up demos and performance.

    Copyright:

    © All Rights Reserved
    Download as PDF, TXT or read online from Scribd
    Flag for inappropriate content
    Download as pdf or txt
    of 1

    Sprint 13 Retrospective | Date: 6/10/22

    START STOP CONTINUE

    What should the team start doing? What should the team stop doing? What should the team continue doing?

    allow for extra  schedule a 


    time for  placeholder meeting 
    pushing 
    deployment in  with business for  to streamline 
    our planning -  feedback mid-​sprint  business to 
    the 
    maybe add in two  - maybe this isn't  engage and 
    with everyone deployment 
    days create in the 
    process boards

    think about how 


    to handle  long term 
    business review 
    scheduling for 
    when more 
    department  asynchronous 
    departments 
    involved engagement remediation

    make 
    do an internal  homework part 
    walk-​through  of the end of 
    prior to  every business 
    business  review
    meeting

    consider utilizing 
    investigate 
    more production 
    ways to speed  data/ 
    up demos/  environment for 
    performance business review

    You might also like