Name: Estimation in LeSS (vs. 'copy & paste' Scrum). More accuracy? Less variability?
Start: 2019-01-15T17:30:00-05:00
End: 2019-01-15T19:30:00-05:00
Location: TEK Systems

Important: Personal ID for building security is a MUST.
------------------------------------------------------------------------------------------------------
Attention: New, great venue! Great hosting by TEKSystems (expect valuable networking)! Snacks & refreshments.
------------------------------------------------------------------------------------------------------
Work estimation in LeSS (vs. 'copy & paste' scrum). More accuracy? Less variability?

Work estimation by one Scrum team could be challenging. Typical issues that Scrum teams face are:

-What scale or measuring technique should we use? Story points? Dog breeds? T-shirt sizes? Days/hours? Both?
-Do we estimate size or complexity? Or both?
-How to make sure that team members with different core skill set and domain expertise meaningfully contribute to estimation by the rest of the team?
-When to do Velocity-driven planning and when to do Capacity-driven planning? Or are they just two stages in the same process?
How to use Historical Velocity to plan your next sprint vs. do longer-term strategic planning?
------------------------------------------------------------------------------------------------------
If the above questions, usually faced in basic Scrum, are not challenging enough, please consider the following additional challenges, faced by multiple teams that are involved in estimation and planning. Some of the questions to consider:

-Are teams involved in proper scaling (Large Scale Scrum), with multiple teams working on the same cadence, on the same product/service, for the same Product Owner? Or are teams involved in ad-hoc "copy & paste" scrum, without any interaction, without having anything in common? (btw, what is 'copy & paste' Scrum?..: https://dzone.com/articles/common-mistakes-when-scaling-scrum)
-Are teams involved in proper scaling (Large Scale Scrum), with multiple teams working on the same cadence, on the same product/service, for the same Product Owner? Or are teams involved in ad-hoc "copy & paste" scrum, without any interaction, without having anything in common?
-What LeSS internal dynamics, events and interactions make LeSS estimation more reliable than estimation by 'copy & paste' Scrum teams?
What specific LeSS guidelines help with the above?
Is multi-site LeSS - a problem?

-----------------------------------------------------------------------------------------
Side Note: please mark your calendars: 05/15-17 – Certified LeSS Practitioner (CLP) | NYC, with Craig Larman: https://less.works/course-details/certified-less-practitioner-new-york-1000

Gene Gendel

Lean, Agile and Large-Scale Product Development (LeSS)

Technology

Software Development

Extreme Programming

Scrum

Agile Project Management

Test Driven Development

Agile Testing

Kanban

Lean Startup

Agile Coaching

Lean Project Management

Agile Leadership

Agile Transformation

Agile and Scrum

Estimation in LeSS (vs. 'copy & paste' Scrum). More accuracy? Less variability?

TEK Systems

Share

Lean, Agile and Large-Scale Product Development (LeSS)

Estimation in LeSS (vs. 'copy & paste' Scrum). More accuracy? Less variability?

Lean, Agile and Large-Scale Product Development (LeSS)

Details

Members are also interested in