Business analysis goes beyond writing user stories… get it right with the techniques from backlogs to wireframes, from use cases to data models, and MoScoW prioritisation to tee-shirt sizing estimation! Texavi's Tech Bootcamp will equip you to be job-ready with practical and real-time insights, as well as offering access to our treasure of insightful, high-quality resources and materials. In this part of the course, we will discuss the nuances that would help us understand the different methods, techniques and tools in software estimation. Though we will discuss the broader estimation aspects, focus is on agile estimation methods and techniques such as user story points, relative size estimation, planning poker, tee-shirt sizing and more.

1. www.texavi.co.uk

2. www.texavi.co.uk 2www.texavi.co.uk
Welcome to Texavi!

3. www.texavi.co.uk 3
First thingsfirst!
www.texavi.co.uk
• This is a freecourse, but rememberthereis no freelunch!
• Its completely developed and delivered by Texavi. No sponsors, help us with youractive participation and support!
Texavi,Analyst-Zone,AZcircle,NewAgeAgileBusiness Analyst*areregisteredtrademarksof TexaviInnovative Solutions

4. www.texavi.co.uk 4
Please remember!
www.texavi.co.uk
• Attend all sessions without fail. Theyareinter-related, so you can get the best only if youattend eachone of them
• Full attendance will open avenues for you! Eg., prepare youfor that BA job interview, certificates, premiumaccess
to ourdigital platform, mobile app,discount vouchers to our online coursesand manymore…
• Do thetasks, exercises and home works. It’s a good investment for you!
Find us, follow us on all popular social/professional media platforms:
YouTube, Facebook, Instagram, Twitter, LinkedIn & coming soon on WhatsApp

5. www.texavi.co.uk www.texavi.co.uk
5
Agenda
 Overview andsetting thecontext
 Factorsthataffectestimation
 Inputsandoutputsforestimation
 Top-downandbottom-upestimation
 Popularmethodsin estimation
 Agile methodsandrelativeestimation
 Principlesofagile estimation
 User storypoints
 Planningpoker
 Best practicesin agileestimation

6. www.texavi.co.uk
6
Agenda
 Overview and setting the context
 Definitions of business analysis
 Business analysis as your career
 Role(s) of a business analyst
 Responsibilities & key tasks of BA
 Summary– Q & A

7. 7www.texavi.co.uk

8. www.texavi.co.uk
8
Agenda
 Recap from last session
 Value-add and benefits from BA
 Where do we need BA
 Core skills of BA
 Behavioural competencies
 Business-related skills
 Essential knowledge/techniques
 Summary– Q & A

9. www.texavi.co.uk 9

10. www.texavi.co.uk
10
Agenda
 Recapfromlastsession
 Key activities & tasks done by BA
 BA’srolein productdevlifecycle
 Dangerstoavoid in BAlandscape
 BA andtherequirementslifecycle
 IIBA – BABOKBA Lifecyclemethodology
 BCS– BAPMmethodology
 BA's rolein theagile methods
 Summary–Q&A

11. www.texavi.co.uk 11

12. www.texavi.co.uk
12
Agenda
 Useful tips, insights,do’s & don’ts
 Essential techniques forBAs
 Essential BAtools& applications
 Techniques inRequirements mgmt
 Bustingmyths &misconceptions
 AgileBA - Estimation& prioritisation
 Wireframes, prototypes& models
 Datamodels andanalytics
 Roadahead- Agiledevcourse

13. www.texavi.co.ukwww.texavi.co.uk 13

14. www.texavi.co.uk www.texavi.co.uk
14
Agenda
 Overviewand settingthe context
 Factorsthataffectestimation
 Inputsandoutputsforestimation
 Top-down& bottom-upestimation
 Popularmethodsin estimation
 Agile methods& relativeestimation
 Principlesofagile estimation
 User storypoints
 Planningpoker
 Best practicesin agileestimation

15. www.texavi.co.uk 15www.texavi.co.uk

16. www.texavi.co.uk 16
What is estimation
www.texavi.co.uk

17. www.texavi.co.uk 17
What is estimation
www.texavi.co.uk
• A roughidea
• High level plan
• Opinionbasedon instincts?
• Measure(s) for layinga roadmap

18. www.texavi.co.uk 18
What is estimation
www.texavi.co.uk
Quantified evaluation of the efforts that is necessary to perform a designated development task.
Indicationof the (overall) size, effort, duration and/or cost of a software project

19. www.texavi.co.uk 19
Why estimation
www.texavi.co.uk
• Journeyfromhazyto asharperpicture

20. www.texavi.co.ukwww.texavi.co.uk 20

21. www.texavi.co.uk 21
Example:Paintyour house
www.texavi.co.uk

22. www.texavi.co.uk 22www.texavi.co.uk
Example:Build an ecommerce web site (Mobile accessories)

23. www.texavi.co.uk 23www.texavi.co.uk
Example:Build an ecommerce web site (Sell Mobile accessories)

24. www.texavi.co.uk 24www.texavi.co.uk
Example:Build an ecommerce web site (Sell Mobile accessories)

25. www.texavi.co.uk 25www.texavi.co.uk
Example:Build an ecommerce web site (Sell Mobile accessories)

26. www.texavi.co.uk 26
Who estimates
www.texavi.co.uk
Persons doing theworkshould estimate!
In IT context,Development Team estimate…
• User storiesin thesprintbacklog
• Tasks/changes/defects…insprintplan
• High level estimatesin productbacklog
Estimationis bestperformed:
• As agroupreaching consensus
• Whenteam userelativeestimation

27. www.texavi.co.uk 27
Questions toanswer
www.texavi.co.uk
• How much effortisrequiredtocompleteanactivity?
• How much calendardaysareneededtocomplete atask?
• Whatis thecostofan activity?
• Whatis thetotalcost todevelop/supportall thefeatures?
ANDMOSTFUNDAMENTALOFTHEM ALL…
• Whatis thesize of workinvolved?

28. www.texavi.co.uk 28
How toestimate
www.texavi.co.uk

29. www.texavi.co.uk 29
Approaches toestimation
www.texavi.co.uk
• Top-downestimation
• Bottom-upestimation
• Absoluteestimation
• Relativeestimatoon

30. www.texavi.co.uk www.texavi.co.uk
30
Agenda
 Overview andsetting thecontext
 Factors that affect estimation
 Inputsandoutputsforestimation
 Top-down& bottom-upestimation
 Popularmethodsin estimation
 Agile methods& relativeestimation
 Principlesofagile estimation
 User storypoints
 Planningpoker
 Best practicesin agileestimation

31. www.texavi.co.uk 31
Factors affectingestimation
www.texavi.co.uk
• Skills available
• Architecture
• Whichlife cycle/methodology
• Maturityofprocesses
• Processstability
• Tools/level ofautomation
• Users’knowledgeofapplication
• Imposed/expecteddelivery dates
• Portability/numberof platforms
• Reliabilityrequired
• Continuityofstaff
• Involvement ofusers
• Teamcohesion
• Location& communicationfacilities

32. www.texavi.co.uk www.texavi.co.uk
32
Agenda
 Overview andsetting thecontext
 Factorsthataffectestimation
 Inputs and outputs for estimation
 Top-down& bottom-upestimation
 Popularmethodsin estimation
 Agile methods& relativeestimation
 Principlesofagile estimation
 User storypoints
 Planningpoker
 Best practicesin agileestimation

33. www.texavi.co.uk 33
Inputs & outputs for estimation
www.texavi.co.uk
Requirements
Schedule –date of
delivery
Effort in person months Skills ofpersons
Number ofdefects Staffing plan Methodology Customer involvement
Cost/budget Tools used

34. www.texavi.co.uk www.texavi.co.uk
34
Agenda
 Overview andsetting thecontext
 Factorsthataffectestimation
 Inputsandoutputsforestimation
 Popularmethodsin estimation
 Top-down & bottom-up estimation
 Agile methods& relativeestimation
 Principlesofagile estimation
 User storypoints
 Planningpoker
 Best practicesin agileestimation

35. www.texavi.co.uk 35
Top-down estimation
www.texavi.co.uk
Estimating by analogy
Relatively quick andeasy todo
Ideal forearly lifecycle phases
(Pre-project, Feasibility and
Requirements)
Uses visible/perceivable features to
estimate size
Depends on skill andexperience of
estimator(s)
Items ofsimilar size groupedtogether
Example:
Senior management’s view on cost
estimates of new project (based on earlier,
similar project)

36. www.texavi.co.uk 36
Bottom-upestimation
www.texavi.co.uk
Each component broken intoindividual elements andeffort estimated against each component and
accumulated
• Decomposition ofcomponents may be:
• By tasks (work breakdown structure - WBS)
• By modules (product/architecture breakdown)
NOTE: Top-down &Bottom-up estimates forthe same
piece of work/project will differ
Mostprecise formofestimating, as each task is estimated separately
Example: Development team in agile dev use Planning Poker forcoming up with user story
points before sprint planning.

37. www.texavi.co.uk www.texavi.co.uk
37
Agenda
 Overview andsetting thecontext
 Factorsthataffectestimation
 Inputsandoutputsforestimation
 Top-down& bottom-upestimation
 Popular methods in estimation
 Agile methods& relativeestimation
 Principlesofagile estimation
 User storypoints
 Planningpoker
 Best practicesin agileestimation

38. www.texavi.co.uk 38
Popular estimationmethodologies
www.texavi.co.uk
• WidebandDelphi method
• Workbreakdownstructure(WBS)
• Sourcelines ofcode(SLOC)
• FunctionPoint(FP) - COSMIC FP
• COCOMO II Model
• Usecasepoints(UCP)
• User StoryPoints(USP)

39. www.texavi.co.uk 39
Wideband Delphimethod
www.texavi.co.uk

40. www.texavi.co.uk 40
Source Lines of Code (SLOC)
www.texavi.co.uk

41. www.texavi.co.uk 41
Work breakdown structure
www.texavi.co.uk
• Typeof bottom-up estimation
• Performed by theteam who do the work
• Detailed de-composition of the product into…
• Modules/features
• Components/interfaces
• Processes/procedures
• Activities, tasks and sub-tasks(?)
Examples:
• Story point estimation
• Planningpoker

42. www.texavi.co.uk 42
Function points(FP)
www.texavi.co.uk
• Arriveat the size, productivity, effort...in that order
• To achievethe above, team identify and count thefollowing :
• Inputscreens/pages i.e., forms
• Output screens/pages i.e., views/reports
• Database tables – referred/updated
• Records and fields inthe database tables
• Team workingon estimates focus on the functionality,
typically referred to as CRUD.
• Create
• Read/Review
• Update (Modify)
• Delete

43. www.texavi.co.uk 43
Usecase points(UCP)
www.texavi.co.uk

44. www.texavi.co.uk 44www.texavi.co.uk
Identify Actors
andUse cases
Rate Complexity of
Actors
Rate Complexity of
Use cases
‘Transaction
based Factors’ Total
Total
Actor Weight
Unadjusted
Usecase Points
Technical
Factors
Environmental
Factors ofTeam
Technical Complexity
Factor(TCF)
Environmental
Factor (EF)
Size in
UseCase Points

45. www.texavi.co.uk www.texavi.co.uk
45
Agenda
 Overview andsetting thecontext
 Factorsthataffectestimation
 Inputsandoutputsforestimation
 Top-down& bottom-upestimation
 Popularmethodsin estimation
 Agile methods & relativeestimation
 Principlesofagile estimation
 User storypoints
 Planningpoker
 Best practicesin agileestimation

46. www.texavi.co.ukwww.texavi.co.uk 46

47. www.texavi.co.ukwww.texavi.co.uk 47
Relativeestimation
• Sizing is done on a relative scale – for better and quicker
outcomes
• Team workingon estimates simply classify the items
usually into 3 categories:
• Big
• Small
• Uncertain
• Effort follows from sizing using productivity (in agile
context, team velocity)

48. www.texavi.co.uk www.texavi.co.uk
48
Agenda
 Overview andsetting thecontext
 Factorsthataffectestimation
 Inputsandoutputsforestimation
 Top-down& bottom-upestimation
 Popularmethodsin estimation
 Agile methods& relativeestimation
 Principles of agile estimation
 User storypoints
 Planningpoker
 Best practicesin agileestimation

49. www.texavi.co.uk 49
Principles
www.texavi.co.uk
• Theagiledevelopment andestimationtechniquesusedare
adoptedbythe entireteam
• This isdoneso astoavoid anysingle personbeing held
responsible
• Agile techniques arecomparativelyquicker thanotherestimation
methodologies
• TeamspracticingAgile prefertominimise estimationandfocus
onaccuracy
• Butwhen estimating,theseteamsarenotestimatingin days
ormoney.Instead,theyestimatethe levels atwhich anitem
mustbeplacedtoget good results

50. www.texavi.co.uk www.texavi.co.uk
50
Agenda
 Overview andsetting thecontext
 Factorsthataffectestimation
 Inputsandoutputsforestimation
 Top-down& bottom-upestimation
 Popularmethodsin estimation
 Agile methods& relativeestimation
 Principlesofagile estimation
 User story points
 Planningpoker
 Best practicesin agileestimation

51. www.texavi.co.uk 51
Story points(SP)
www.texavi.co.uk
A storypointis a measureofthe size
• Morepractically it’stheteam efforttoworkonaset
ofitems
• Scale ofpointsagreedandset bythe team.Usually
basedonthe benchmarkoftheir velocity (i.e., team
productivity)
• Example…howmuch worktheycan doin aday
• “Work”need notalwaysbecoding butmostoftenit
is

52. www.texavi.co.uk
Story points(SP)
www.texavi.co.uk
When estimating, team use a relativegrading system in
numbers
• A task that has 3points should takethreetimes the effort
for that of with 1 point
• A 20point task twice the effort of a task that has 10
points
Story points represent the effort, so duringestimation/planning the team need to consider…
• Size of the work involved
• Quantumof workneeded
• How complex the work is
• Thepotential risks involved

53. www.texavi.co.uk www.texavi.co.uk
53
Agenda
 Overview andsetting thecontext
 Factorsthataffectestimation
 Inputsandoutputsforestimation
 Top-down& bottom-upestimation
 Popularmethodsin estimation
 Agile methods& relativeestimation
 Principlesofagile estimation
 User storypoints
 Planningpoker
 Best practicesin agileestimation

54. www.texavi.co.ukwww.texavi.co.uk 54

55. www.texavi.co.uk 55www.texavi.co.uk 55
Planningpoker – How toplay
www.texavi.co.uk
• Based on Fibonacci series of numbers 0,1,2,3, 5, 8,13,21…
• Each team membergets a deckof cards with numbers
1. PO/BA reads the userstory and explains the feature(s) and
scenarios/acceptance criteriaetc.
2. Estimators (team members) discuss the features
3. On the count of 3,2,1…estimators show their own card by holding it infront
so all could see
4. Majority rulesand agreementis arrived
5. If 4 is not done, thenrepeat steps no.1 through4
6. Consensus is reached – yay!

56. www.texavi.co.uk www.texavi.co.uk
56
Agenda
 Overview andsetting thecontext
 Factorsthataffectestimation
 Inputsandoutputsforestimation
 Top-down& bottom-upestimation
 Popularmethodsin estimation
 Agile methods& relativeestimation
 Principlesofagile estimation
 User storypoints
 Planningpoker
 Bestpractices in agile estimation

57. www.texavi.co.ukwww.texavi.co.uk 57
Beforeestimatingscope-in and scope-out

58. www.texavi.co.ukwww.texavi.co.uk 58
• A measureoftherateatwhich individualengineers involved in softwaredevelopment produce
softwareandassociated
documentation
• Notquality-orientedalthoughqualityassuranceis afactorin productivityassessment
• Essentially,we wanttomeasureusefulfunctionalityproducedpertimeunit
Productivity

59. www.texavi.co.ukwww.texavi.co.uk 59
Use relativeestimationas much as possible

60. www.texavi.co.ukwww.texavi.co.uk 60
Tee-shirt sizing
• The processstartsbyspecifying theitems withasize {XS,S,
M,L, XL,XXL}
• Insteadofletters,teamcanusenumberformats(1, 2,3
etc.,) ifitismoreconvenient
• The techniquecanbe usedeasily andquicklyonanyitems
(i.e., stories,tasks,changes,defects)
• Priortothe exercise, team mustdiscussanddecide onthe
definition/benchmarkforeach sizeindicator(e.g.., what
doesasmall item mean vis-à-visalargeitem)

61. www.texavi.co.uk
Thank you!
Texavi Innovative Solutions
The new age people for new age solutions!
Consulting | Training | Solutions
Regd. Office
Texavi Innovative Solutions (UK) Ltd
36 Glebe Road
Finchley
London N3 2AX
Email: connect@texavi.co.uk
training@texavi.co.uk
connect@analyst-zone.com
Connect with Texavi
www.texavi.co.uk
https://analyst-zone.com
www.facebook.com/texavi
Twitter @pardhas
LinkedIn Texavi
Blog www.texavi.com/blog