the agile ba presentation · 7/21/16 1 the agile ba we are: • 300+ improvers • software...
TRANSCRIPT
7/21/16
1
TheAgileBA
Weare:• 300+Improvers• SoftwareDevelopers• Agilists• IndustryThoughtLeaders• EducationProviders
WhereistheBA?
7/21/16
2
TheBAIdentityDilemma
• Coderscode• Testerstest• WhatdoBA’sdo?
..andaretheynecessary?
RequirementsSpecialistorGeneralist?
BusinessProcessModeling
Facilitating
DomainModeling
AcceptanceCriteria
UserStories
StoryBoarding
DataModeling
BusinessModeling
BusinessAlgorithms
Writing
Organizing
Interviewing
Abstraction
RootCauseAnalysis GapAnalysis
DataElementSpecification
ROIAnalysis
WorkflowAnalysis
Industry/DomainExpertise
SWOT
FinancialModeling
GENERALIST
SPECIALIST
Speaking
DecisionMatrix
Couldbefulfilledbyanyteammember
BAasthe ProductOwner
Why?Businessunabletocommitsomeonetotherole.
Viableif…
• BAisqualifiedtomakebusinessdecisions.
• BAisempoweredtomakescope/budget/prioritizationdecisions.
• BAisastakeholderinthesuccessofthebusiness.
• BAisinbusinessorganizationalhierarchy.
7/21/16
3
BAasProxy ProductOwner
Why? Disconnected/unavailableproductowner.
Risks:
• Couldberedundant.
• Latencyindecisionmaking.
• Informationcangetlostintranslation.
• Bottleneck/blockifnotempoweredtomakedecisions.
Scrum.org ProductOwnerAdvice:Expectedbenefits
Yes,And…NOT
Scrummini-CEOBusiness
withMandate
BusinessRep
ProxyAnalyst
*FromScrum.org’sProfessionalScrum
Mastercourse
BAasDevTeamMember
SPRINT1
SPRINT2
SPRINT3
T4
Helpdevelopersandtesterswithcurrentsprint.
Prepareforthenextsprint.
Solicitfeedbackoncompletedsoftwareincrementsto-date.
ManagingComplexityI need you to build us an accounting system.
Sounds like a pretty straightforward domain.
7/21/16
4
Remember:It’snotthefirstlayerthat’sbothersome.
7/21/16
5
Wherearetherequirements?
Yourself
ProductOwner
Accountants
DomainExperts
CFO
OtherSME’s
Executives
Software/Systems
Customers
DemystifyingComplexThings
LeverageExistingOntologiesPublisheddomainvocabularies,entities,andrelationships.
DemystifyingComplexThings
Animal
Canine
Dog
Dalmation
UseAbstraction
DemystifyingComplexThingsStayIsomorphicFabricatingentitiesandconceptsthatdon’tmatchtherealworldcanoverlycomplicatethetargetsystem.
7/21/16
6
Thegoal:Target
SoftwareSystem
KnowledgeSkills
ExpertiseStrategyCreativity
Asfewstepsaspossible!
Why?
Asa<businessrole>Iwill<dosomebusinessfunction>Sothat<businessvalue>
7/21/16
7
perhapsnottoobrief..
ThinkofaUserStoryas..
Thisworkswhenthecomposerisalsothe
performer…
7/21/16
8
Butforanyoneotherthanthecomposer…
P SW
TRYTHIS:
Drawapizzathathaseightsliceswiththreelines.
7/21/16
9
Whatisfairweather?
7/21/16
10
Kennedy:“Whatisthe
CIA’sassessment?”
Bissel:“Wehaveafairchanceofsuccess.” Asauserofthesystem
Icanclickfile-saveSothatstuffissaved.
Clear?Useful?
7/21/16
11
Whatifit’snight?Raining?Foggy?Eclipse?
EffectiveBrevitycanbedifficult…
“IfIhadmoretime,Iwouldhavewrittena
shorterletter.” Pascal,etal
7/21/16
12
TABOOteapotshortstoutcoffeewaterheat
TABOObedbunksleepmattressstepsdrawerstopbottom
TABOOmotorcyclebikecamperhouseRVtrailerchopperHarley
7/21/16
13
Isitbestto…Writethemdown?
Talkaboutthem?
Drawthem? Performthem?
7/21/16
14
Nomatterhowmuchyou…Thinkabout
Writedown
Draw
Talkabout
Develop
Demonstrate
Deploy
Requirements…
That’s
why
we
iterate...
Knowledge Howdowebest:- Communicate?- Learn?- Understand?- Retain?
7/21/16
15
MostBA’sknowtheymust:
Solicit requirements
Capture requirements
Record requirements
Organize requirements
Elaborate requirements
BA’sshouldalso :
Bestewardsofthebacklog
Embracerequirementschanges
Eliminateambiguity
Helpothers understandrequirements
Isthishowyoucommunicate?
7/21/16
16
VARK:Whichareyou?
Visual
Auditory
Reading/Writing
Kinesthetic
©1995,NeilFleming,LincolnUniversity
Visual
Auditory
Reading/Writing
Kinesthetic
Knowingyour fellowteammembers’VARKis
….aBASuperpower!!
BA’scommunicatealot!andknowingyourVARK
canbeuseful...
7/21/16
17
Understandsbestby:• Takingnotesandmakingliststoreadlater• Readinginformationtobelearned• Learningfrombooks,videotapes,filmstripsandprintouts
• Seeingademonstration
Isgoodat:• Rememberingdetailsandcolorsofwhathe/shesees
• Reading,spellingandproofreading• Rememberingfacesofpeoplehe/shemeets(forgetsnames);remembersnamesseeninprint
• Quietlytakinginsurroundings• Creatingmentalphotos
Understandsbestby:• Talkingaloud• Listeningtoalecture• Discussinginsmallorlargegroups• Hearingmusicwithoutwordsasabackgroundinthelearningenvironment
7/21/16
18
Isgoodat:• Speakingonhis/herfeet• Noticingsoundsinenvironment• Rememberingnamesofpeoplehe/shemeets(forgetsfaces)
• Workingwithwordsandlanguages• Tuningintosmallshiftsinvoiceintonation
Understandsbestby:• Readingandwriting• Readingandre-readingbooksandarticles• Writingandrewritingnotesthey’vetakenIsgoodat:• Organizinginformation• Beingthoroughanddetailed
Learnsbestby:• Processinginformationtroughtouch,movementandrhythmicmovements
• Doinghands-onactivitiessuchaswoodshop,dance,and/orathletics.
Isgoodat:• Expressingideasthroughmovement• Fine-motorskills• Demonstratingbydoing
7/21/16
19
UserStories
DailySCRUM
PlanningMeetings
Backlogs
StoryEstimation
Reviews/Demos
Wireframes/Storyboards
Models/Diagrams
Burndown/upCharts
Theuserstoryisastart…
…butwhatelse?
SkillfulBA’scommunicate…
…likemapmakers
OR=
7/21/16
20
WhatisaMap?
A representation of the features of anarea from a physical (often geographical),logical, or conceptual domain, showingthose features in their respective forms,sizes, and relationships according to someconvention of representation.
2300BC
BabylonClayTablets
Oldestacknowledgedmaps
7/21/16
21
350BC
Aristotle
FirstrepresentationoftheEarthasasphere
85ADPtolemy
Madeasubjectivedecisionthataffectsallofus,
andmaybeimpossibletoeverchange.
1569GerardusMercaturSkewedourviewoftheworld.
BETTER!
7/21/16
22
2005GoogleCorporationHelpedmakeinteractivemapsanessentiallifetool.
WARNING:Incorrectmapscansteerpeoplewrong…
WhyBuildMaps? WhyBuildMaps?
7/21/16
23
Somemapsdescribestructure… Somemapsdescribeprocess/behavior…
Somemapscandescribetheunseen…Human
ChromosomeElectionResults
MindMap
FictionalPlaces
“ The map doesn’t let us see anything,
but it does let us know what others have seen or found out or
discovered. “
Denis Wood
7/21/16
24
AvoidMyopiaWhatLetterisshownbelow?
AvoidMyopia
Tip:Don’tAvoidSurroundingContext
Includeafewelementsoutsidethetargetscopeiftheyhelpestablishpropercontext.
Software/SystemMaps
Oftenreferredtoasmodels…
• Somedepictstructure
• Othersdepictbehavior
7/21/16
25
FromStorytoSoftware…
DomainMaps SystemMaps
CANBERISKY
WorksbestwhenallareAuditorylearners
UserStory
DomainModel
UseCase-
Epic
DETAIL
low
highTests
DataMaps
OtherModels
StoryBoards
DataDefinitions
BizRules
“Aremindertohavea
conversation”Detailed
RequirementsSpecifications
UserStory
DomainModel
UseCase-
Epic
DETAIL
low
highTests
DataMaps
OtherModels
StoryBoards
DataDefinitionsBiz
Rules
“Aremindertohavea
conversation”
DetailedRequirementsSpecifications
Whenarewritten
detailsneeded?
Howmanyofthese
areuseful?
ComplementaryMapscanHelp
7/21/16
26
Creatinganewproductbacklog?
Trystartingwitha
UseCaseDiagram
EXAMPLE
Candidate
epics
Complexdata?
Tryadomainmodel.
EXAMPLE
Describingabusinessprocess?
YoucandepictusingBPMN.
EXAMPLE
Employ
eeMan
agerCo
mpa
ny
Per-Diem
Cacu
lator
www.gsa.gov
RecordExpenses
CalculateTotal
CalculatePer-Diem
SubmitExpenseReport
UtilitarianService--Encapsulatedandloosely
coupled.
ApproveExpenseReport
…and/orstoryboards
7/21/16
27
• Decompositionofthings• Relationshipsbetweenthings• Multiplicity• Variedabstractionlevels
– Highdetailforsomethings– Littledetailforothers
Examples:– ERD- Datamodel– UMLObjectmodel– UMLDomainmodel– Mindmap– UMLDeploymentDiagram– SoftwareClassDefinition
StructuralSoftwareMaps BehavioralSoftwareMaps
• Processes&Activities• Messages,Events&Triggers• Flow:Sequenceand/orConcurrency
Examples:– UserStory– UseCase– SequenceDiagram– CollaborationDiagram– ActivityDiagram– StateDiagrams– BusinessProcessDiagram– RunBooks– SoftwareMethod Online Store
Browse Catalog
Buy Items
Ship Items
Customer
ShippingDepartment
CustomerService Rep
WARNING: Don’toverdoit!
Remember:Acomprehensivemapisnot theendgoal!
ThistookMichelangelofouryears!
7/21/16
28
Trywhiteboardmodeling…
Useittoenhanceconversations.
Andlearntochunkeffectively
Often
overlooked
AgilePrinciple#1:Ourhighestpriorityistosatisfythecustomerthroughearlyandcontinuousdeliveryofvaluablesoftware.
• Developrequirementstop-down.• Elaboratestoriesjust-in-time.• Treatstoriesasreferencestoworkingsoftware-nomore,noless.
TIPSFORTHEAGILEB.A.
7/21/16
29
AgilePrinciple#2:Welcomechangingrequirements,evenlateindevelopment.Agileprocessesharnesschangeforthecustomer'scompetitiveadvantage.
• Addnew/revisedstoriesasrequestedbytheProductOwnerwithoutcomplaint.• Alwaysprioritizeandshift“lesser”storiesdownthelist.
TIPSFORTHEAGILEB.A.
AgilePrinciple#3:Deliverworkingsoftwarefrequently,fromacoupleofweekstoacoupleofmonths,withapreferencetotheshortertimescale.
• Becomegoodat“chunking”.• Coach/urgethebusinesstoembracesmallusableincrements.• Haveaclearconcrete“DefinitionofDone”
TIPSFORTHEAGILEB.A.
7/21/16
30
• Encouragebusinessfolkstobeactivelyinvolvedcontinuously,notjustondemodays.• BeempathetictotheSMEandPO’sothercommitments;Trytoworkaroundtheirschedules.
TIPSFORTHEAGILEB.A.
AgilePrinciple#4:Businesspeopleanddevelopersmustworktogetherdailythroughouttheproject.
• Offerencouragement;don’tcomplain.• Chipintohelpthosewhoarebehind.• Dotasksthatnobodyelsewilldo.• Ask“Whoneedshelp?”“HowcanIhelp”
TIPSFORTHEAGILEB.A.
AgilePrinciple#5:Buildprojectsaroundmotivatedindividuals.Givethemtheenvironmentandsupporttheyneed,andtrustthemtogetthejobdone.
7/21/16
31
AgilePrinciple#6… Group1
FolderInstructor
Group2
Folder
Instructor
Group3
Folder Instructor
7/21/16
32
TIPSFORTHEAGILEB.A.
Agile Principle #6:AgilePrinciple#6:Themostefficientandeffectivemethodofconveyinginformationtoandwithinadevelopmentteamisface-to-faceconversation.
• Choosetalkingoverwriting.• Usewritingasaremindertoyou,notothers.• Prepareforalotofredundancy.• Chooseface-to-faceoverphone,Skype,IM.
• Treatrequirementsasameanstoanend….notanendinitself.• Eliminateallworkthatdoesn’tcontributetothecreationofworkingsoftware.
TIPSFORTHEAGILEB.A.
AgilePrinciple#7:Workingsoftwareistheprimarymeasureofprogress.
7/21/16
33
• Chunkrequirementsasmuchaspossible.• “Feed”chunkstodeveloperscontinuously.• Avoidhavingotherswaitforrequirements.
TIPSFORTHEAGILEB.A.
AgilePrinciple#8:Agileprocessespromotesustainabledevelopment.Thesponsors,developers,andusersshouldbeabletomaintainaconstantpaceindefinitely.
• Supportdevelopers’“thinktime”.• Helpremoveblockstotechnicalexcellence.• Speculatefuturemodificationstohelpdesignersbuildforeaseoffutureenhancements.
TIPSFORTHEAGILEB.A.
AgilePrinciple#9:Continuousattentiontotechnicalexcellenceandgooddesignenhancesagility.
• Helpsellthebusinessonincrementalfeatures.• Utilizethe80/20rulewhenprioritizing.• Acceptthatmusthave’saren’talwaysamust.• Helpthebusinessembracechange.
TIPSFORTHEAGILEB.A.
AgilePrinciple#10:Simplicity— theartofmaximizingtheamountofworknotdone— isessential.
• Minimizetimebetweenneedandaction,don’twaittobetoldwhattodo.• Dowhatyouknowneedstobedone.
TIPSFORTHEAGILEB.A.
AgilePrinciple#11:Thebestarchitectures,requirements,anddesignsemergefromself-organizingteams.
7/21/16
34
• Betransparent.• Encouragetransparencyinteammates.• Supportretrospectives,andfollowthrough!
TIPSFORTHEAGILEB.A.
AgilePrinciple#12:Atregularintervals,theteamreflectsonhowtobecomemoreeffective,thentunesandadjustsitsbehavioraccordingly.
Questions?
Thanks!
www.improving.comwww.AgileIntrovert.com