Building your own catalog Live long and prosper
Building your own catalog “Live long and prosper”
About me § Employed with Kinetic Data ~2 years § Level 29 Code Wizard § 15+ years programming experience § Love Kinetic Data 3
Agenda § About this presentation § About ERM Catalogs § Take Inventory § Gather Requirements § Scope the requirements § Plan for the future § Questions 4
About this presentation § Help understand ‘catalogs’ § Steps to help deploy catalog project § Steps to help the future of the catalog 5
ERM Catalog overview § Central website for submitting requests § Website for showing status of requests § Any kind of business request § www. erm. info 6
ERM Catalog overview http: //www. youtube. com/watch? v=2 Csm. Eg_n 2 n. E? rel=0 7
Taking Inventory § Overview § Reasons to take inventory § How to take inventory 8
Taking Inventory § Reasons to take inventory § Ensures you don’t go backwards § Helps you move forward § Helps frame requirements gathering 9
Taking Inventory § How to take inventory § Browse what you already have § Recording various webpages § Noting what you don’t have § Note commonality 10
Requirements Gathering § Overview § Reasons to gather requirements § Common requirement ‘categories’ § Make the list – need it, want it, got it. 11
Requirements Gathering § Reasons to gather requirements § Makes sure you don’t miss something (Inventory!) § Helps ensure you deliver is what is wanted § Helps generate templates for efficient development § Helps with scoping later on 12
Requirements Gathering § Common requirement ‘categories’ § Branding § UI § Identity, Authentication, Authorization § Service items / Request forms § Post-submission workflow 13
Requirements Gathering § Common requirement category: Branding § Guideline probably already exists § Look for fonts, colors, spacing, logos § Examples of branding guides: § http: //www. udel. edu/cpa/pdfs/brand-style-guide. pdf § http: //walmartlabs. github. io/web-style-guide/ § https: //design. ubuntu. com/web-style-guide 14
Requirements Gathering § Common requirement category: UI § Guideline probably already exists (Technical) § HTML / CSS standards § Pages needed? § Catalog § Search request forms § Search submissions § My Requests / Approvals § Site Feedback 15
Requirements Gathering § Common requirement category : Identity § Things about you § Phone § Email § Physical Address § Title § Direct report / Direct reports § Central source § Contingency plans 16
Requirements Gathering § Common requirement category : Authentication § Simply getting into the website § Pass / Fail § Username / password source § Single sign on 17
Requirements Gathering § Common requirement category : Authorization § Granular rules § For access inside of the catalog § Examples § If user’s country is United States § If user is a VIP § If user is a manager 18
Requirements Gathering § Common requirement category: Service Items § Requested For, Requested By § People data § Auto-populate? § Display? § Editable? § Common questions? (Region, Department) 19
Requirements Gathering § Common requirement category: Post-submission activity § Approvals § Group or individuals § Concurrent vs. chained § People data retrieve § Work order generation § SLA timers § Email templates 20
Requirements Gathering § Make the list § Need it § Financial issues if it isn’t done § Increases efficiency § Want it § It would look cool § Got it § Helps you take a breather 21
Scoping § Overview § Reasons for scoping § How to scope § Prioritize § Make waves –Weee!!! § Scope creep – Booo!!! 22
Scoping § Reasons for scoping § Helps determine workload § Helps determine when to deliver § Helps you deliver on your promises 23
Scoping § How to scope: Prioritize § Simple 1 -5 scale § Want its get 1 -2. § Need its get 3 -5. § Assign to categorizes § Assign to specifics § Helps plan waves 24
Scoping § How to scope: Make waves – Weee!!! § Different kind of waves § Waves in the middle of the ocean § Waves at the shore § People like waves they can see & feel § Many, non-stop, all small, waves § Amazon Echo 25
Scoping § Scope creep § What it is § Why it happens. § People don’t believe in ‘tomorrow’ § We think we can’t say no § Why its bad § How to prevent it 26
Scoping § Scope creep: What it is § Add-ons after scope § Keeps us up late at night § Big or small, they can make you suffer § They delay due dates § Clichés 27
Scoping § Scope creep: Why it happens § People don’t believe in ‘tomorrow’ § We don’t like to say no § We think we can’t say no 28
Scoping § Scope creep: How to prevent it §Step One: STOP IT 29
Scoping § Scope creep: How to prevent it § Stop listening to TLC § Bargain, trade, compromise § Front end vs. rebuild? § “Maybe tomorrow” § But really mean it § Don’t be Wimpy § Give visibility to “tomorrow” http: //agilepm. com/managing-scope-creep-in-agile-projects 30
Planning for the future § Groups vs. Individuals § Create ownership (design & development) § Portal § Catalog § Service Items § Try to delegate service item design & development § Establish a steering community & committee 31
Steering Community 32
Questions? 33
- Slides: 33