Requirements Gathering for SharePoint Developers
•
1 j'aime•130 vues
Learn how to gather requirements for SharePoint development projects
Recommandé
Recommandé
Contenu connexe
Similaire à Requirements Gathering for SharePoint Developers
Similaire à Requirements Gathering for SharePoint Developers (20)
Plus de Rob Bogue
Plus de Rob Bogue (20)
Dernier
Dernier (20)
Requirements Gathering for SharePoint Developers
- 1. Requirements Gathering for SharePoint Developers Robert Bogue (317) 572-5310 Rob.Bogue@ThorProjects.com
- 2. Global Scope
- 5. Not Taking Orders • Accepting Problems Not Solutions • Working Together to Find Solutions
- 8. High Level Project Activities Scoping • Assess effort • Assess impact Requirements • Capture knowledge • Create consensus Design / Architecture • Framework for solution design • Refine estimates Develop / Test • Write code • Test functionality Deliver • Migrate to production • Train users
- 9. Project Deliverables Scoping Project Charter Project Scope Requirements Requirements Requirements Specification Design / Architecture Solutions Architecture Develop / Test Completed Code Test Execution Deploy / Train Deployment Package Training Materials
- 10. Software Development Roles Training Deployment Quality Assurance Developer Development Lead Solutions Architect Business Analyst Subject Matter Expert
- 11. Requirement Types Business Requirement User Requirement Functional Requirement SystemRequirement BusinessRule Constraint Quality Requirement
- 12. Learning Out of the Box
- 13. Content by Search • Full Functionality of Search in a Web Part • Visual Experience via Display Templates • Use to Display Searchable Data
- 14. XML Viewer • Consume XML from Web URL • Transform with XSLT • Caching Built in
- 15. Workflow • Two Workflow Engines • 2007/2010 (Windows Workflow Foundation) • 2013+ (Azure Workflow Services) • Start on • Creation • Change
- 16. Strategy: Build Off Box and Connect • Workflow 2013 • Calls Services • Add-ins • SharePoint Hosted JavaScript • Provider Hosted • Apps • Provider Hosted
- 17. Elicitation
- 18. Games
- 19. References
- 20. Innovation Games Buy a Feature Show and Tell Speed Boat Product Box Me and My Shadow Give Them a Hot Tub Prune the Product Tree Start Your Day The Apprentice 20/20 Vision Spider Web Remember the Future
- 21. Speed Boat Open-Ended Exploration Time Frame of Action Scalability Customer Preparation Market Preparation Physical Preparation • Draw a Speed Boat Representing the Business Process • Have Customers Add Issues Holding the Boat Back (“Anchors”) • Customers Estimate How Much Faster the Boat Can Go Without the Anchor
- 22. Prune the Product Tree Open-Ended Exploration Time Frame of Action Scalability Customer Preparation Market Preparation Physical Preparation • Draw a Tree to Represent the Current Product • Major Areas of Functionality are Large Limbs • Individual Features Are Leaves • Customers Shape the Tree by Adding Features
- 23. Requirements Tools • Persona • Use Case • Wireframe • Storyboard • Mockup
- 24. Persona • Fictional representation for a group or class of users • Personas • Have a name, photo, and backstory • Improve communications • Force deeper thinking
- 25. High-Level Use Case • What the user needs to do • One use case per user class and activity • Personas are the actors, Use Cases are the play
- 26. Wireframe • Block representation of the user interface • Intentionally not sophisticated • Useful for identifying missing requirements
- 27. Wireframe Tools • PowerPoint • Visio • Balsamiq
- 28. Storyboard • Collection of wireframes designed to show lines of action • Leveraged to ensure that use cases are possible • Improves user experience design
- 29. User Experience • How the user experiences the solution • More about the “arrows” and less about the “boxes”
- 30. Prototype • Disposable • Evaluative • Spike
- 31. Abstract and Concrete • We grasp the abstract through means of the concrete • We can better simulate the solution if we can see it
- 32. Paper (not plastic) Prototypes • Quicker to do on paper than in a prototyping tool • No one will see a paper prototype and assume that you’re almost done
- 33. Requirements Tools • Meetings • One-on-one • Interview • Observation • Focus Groups • Presentations • Questionnaires • Open • Closed
- 34. Documentation
- 36. Visuals • Process Flow • Swim Lanes • Data Flow Diagrams • UML State Diagrams • UML Activity Diagrams • Entity Relationship Diagram • Business Process Modeling Notation (BPMN)
- 37. Process Flow InvoiceProcessing Is valid vendor? Has valid contract? Contract $ remaining >= Invoice $ Process Payment Notify Vendor Failure Notify Contract Owner Failure Yes Yes Yes No No No End Notify Vendor Processing Yes Contract Owner Approval? Notify Vendor Rejected No
- 38. Swim Lanes Budget Approval Sales Management Requestor Finance Management Executive Management System Phase Request Budget Establish Budget Appropriate Customer? Risk/Reward acceptable? > 100K Strategic? Reject Review Resubmit? No Yes Yes Yes No Yes No Yes No No
- 39. Data Flow Diagrams Request Budget Request contract Budget Master Contract Master Payment Master Request Payment Budget Approver Request Repository Request Details Approval Budget Allocation Contract Approver Available Budget Approval Contract Allocation Print ContractAvailable Contract Payment Approver Available Contract Approval Payment Allocation Pay InvoiceAvailable Invoice
- 40. UML State Diagrams Draft Pending Budget Budgeted Contracting Contracted Paying Paid Cancelled Cancel Contracts Remove Unused Budget Requester: Request Budget Budget Approver: Approve Budget Manager: Re-review Requestor: Request Contract Requestor: No More Contracts Requestor: Pay Invoice System: No more contracts open Requestor: No more payments Completed Requestor: Project CompletedRequestor: Cancel Project Requestor: Cancel Project Requestor: Cancel Project Requestor: Cancel Project Requestor: Cancel Project Requestor: Cancel Project Requestor: Cancel Project
- 41. UML Activity DiagramsRequest Budget Review Review Risk Strategy Review Reject Establish Budget [Not Appropriate Customer] [Appropriate Customer] [Bad Risk] [Less than 100K] [More than 100K] [Bad Fit] [Good Fit] [Confirmed] Resubmit [Retry]
- 43. Business Process Modeling Notation Request Budget Budget Approved? Request Contract Request Payment Contract Approved? Payment Approved? Create Contract Entry Create Payment Entry Yes No Budget Exists? No Yes Yes Contract Exists? No Yes Yes Budget Request Approved Budget Request Rejected Contract Request Rejected (No Budget) Contract Request Approved Contract Request Rejected No Payment Request Rejected (No Contract) Payment Request Approved Payment Request Rejected No Create Budget Entry
- 44. Block Diagram Operations Accounting Customer Production Warehousing Shipping / Receiving General Ledger Budget Purchasing Relationship Orders Credits
- 45. Ecosystem Map Vendor Management Contract Management Accounts Payable Approval Management Cash Management Budget Management Project Management Product Management General Ledger (Accounting) Production Management Customer Relationship Management Sales Management Inventory Management Order Management Logistics Vendor Availability Terms SelectionRecord Payment Contract Available Product Completion Budget Availability Inventory Availability New Inventory Shippment Customer Details Demand Availability Vendor Resources Payment Approval Order Status
- 46. Imprecise Words / Phrase Imprecise Word / Phrase Comment / Questions / Suggestions Acceptable / Adequate What’s acceptable to you? As much as possible Is this measurable? Best / Greatest Compared to what? Fast / Quick / Rapid How long is that? Improved / Better / Faster / Superior How much better? Quantify Generally / Usually / Almost always What are the rules? What % of the time? Minimize / Maximize / Optimize How much? Law of diminishing returns Normally / Ideally Under what conditions? Optionally Who chooses? Probably Will it or won’t it? Robust Specify behaviors.
- 47. Thank You Robert Bogue (317) 572-5310 Rob.Bogue@ThorProjects.com
Notes de l'éditeur
- Just show me what it does and I’ll tell you what I want
- Kelly Johnson @ Lockheed Martin. U-2 flew higher than rockets (almost), the SR71 Blackbird flew faster. It also “leaked like a sieve” on the ground. 1964->1998 Only 32 built. 12 lost due to accidents.
- Facilitation is a key still – not the expert but allowing the wisdom of the crowd to emerge
- Green = Short Term, Yellow = Medium, Red = Long
- They’re not abstract
- Actors are abstractions for people