Friday 19th June, 2015
11:30am to 12:10pm
Universally, estimating software stories and tasks is hated by developers and most normal people. Almost as universally the results obtained from forecasting using those estimates are dismal. This session begins by listing the top ten reasons why estimation is a flawed approach and then goes onto offer simple alternative techniques. The alternative techniques described are simple to implement and will perform better than traditional estimation (not a high bar), and often better than intuition alone.
By attending this session you will learn –
-The top ten reasons why current estimation fails
-The situations when estimation is irrelevant and misleading (#NoEstimates)
-The difference between forecasting and estimating
-How little data is needed to be better than intuition alone
-Simple forecasting approaches that don’t fail – Monte Carlo Forecasting
Experienced IT executive (CTO/VP).Founder of Focused Objective to build tools for simulating and forecasting software development projects. bio from Twitter
Troy has been involved with technology companies since 1994, fulfilling roles from QA, development through to VP of Technology for multinational companies. Troy speaks at many Agile conferences and has played an Agile training and mentoring role for executives in small and large organizations. Previous clients include: Walmart, Microsoft, Skype, Sabre Airline Solutions, Siemens Healthcare and Tableau.
Troy currently consults and trains organizations wanting to improve decision making on software portfolio and project questions through Agile and Lean thinking and tools. Applying Scrum and Lean techniques appropriately and where they are going to make this biggest benefit through quantitative rigor.
Troy has many books and articles on software development and practices, his most recent is “Forecasting and Simulating Software Development Projects: Effective Modeling of Kanban & Scrum Projects using Monte Carlo Simulation”.
Sign in to add slides, notes or videos to this session