
Bruce Telford
Project Manager/Agile Coach
UKY
location_on United States
Member since 2 years
Bruce Telford
Specialises In (based on submitted proposals)
An Agile transformation coach and leader
-
keyboard_arrow_down
Epic Planning Poker
10 Mins
Lightning Talk
Intermediate
Within Agile Scrum, how do you provide an estimate when you could reach MVP/MMP?
In traditional project estimation, you might complete a full WBS, estimate each element, sum it all up to arrive at total effort, lay out resource and technical dependencies, and finally add in appropriate buffers to get a project completion date.
Since in Agile we iteratively build and refine the tasks and constantly adjust priorities, the traditional way doesn't work. But why do we need to? Because in most organizations, the external budgeting and planning processes have not yet adopted Organizational Agility. Annual cycles of budgeting and planning still wants overall project estimates. Epic Poker extends the Sprint Planning Poker concepts to collections of stories (Epics), and provides a analytic tool to predict how long it might take to get to MVP.
Once there, the Epic Points can then be used to calculate and monitor a modified form of EVM to show progress to stakeholders
-
keyboard_arrow_down
Impedance Matching
45 Mins
Talk
Beginner
For an organization that has not yet embraced Organizational Agility, how do you make IT Agility work?
-
keyboard_arrow_down
Velocity--A little talk on what it is and isn’t, and how to make it meaningful
10 Mins
Lightning Talk
Beginner
Scrum relies heavily on Velocity for planning and performance improvements. Let's talk about what it really means, some anti-patterns and good practices.
One of the more abstract concepts in Agile is how to use Story Points and Velocity. It seems pretty straightforward in concept--assign each work unit (story) relative points; at the end of the sprint count up how many points you completed and plan that number for next sprint. But in practice...
Do points represent days? Complexity? What if something is easy to develop but hard to test? Maybe a task is UI heavy or back-end heavy? Should all teams in an organization use the same scale? What happens when the team composition changes?
One of the most common challenges is how velocity is viewed outside the Scrum team. Why is Team A's velocity 70 while Team B's is 90? How can we increase velocity to 90? Of course the team can and will fix that just by changes the SPs assigned to each task--that three-point story is now magically worth five; how did that happen?
Points and Velocity are just tools. Learn some ways to not let them take over.
-
No more submissions exist.
-
No more submissions exist.