|
|
|
|
| LEADER |
06955nmm a2200457 u 4500 |
| 001 |
EB002137989 |
| 003 |
EBX01000000000000001276116 |
| 005 |
00000000000000.0 |
| 007 |
cr||||||||||||||||||||| |
| 008 |
230102 ||| eng |
| 020 |
|
|
|a 1801810575
|
| 020 |
|
|
|a 9781801810579
|
| 050 |
|
4 |
|a HF5415.5
|
| 100 |
1 |
|
|a Munagavalasa, Srini
|
| 245 |
0 |
0 |
|a The salesforce business analyst handbook
|b proven business analysis techniques and processes for a superior user experience and adoption
|c Srini Munagavalasa
|
| 250 |
|
|
|a 1st edition
|
| 260 |
|
|
|a Birmingham
|b Packt Publishing
|c 2022
|
| 300 |
|
|
|a 1 online resource
|
| 505 |
0 |
|
|a Requirement documentation -- The art of elicitation -- Practical tips for success -- Summary -- Questions -- Further reading -- Chapter 3: Prioritizing Requirements -- The importance of requirement prioritization -- Reviewing prioritization techniques -- MoSCoW analysis -- Story mapping -- Dependency map between requirements -- Managing prioritization meetings -- Practical tips for success -- Simple CRM requirement prioritization and roadmap scenario -- Summary -- Questions -- Further reading -- Chapter 4: Process Flows -- "As-Is" versus "To-Be" -- Reviewing the process flow -- Process flow types
|
| 505 |
0 |
|
|a Get a system walkthrough -- Active participation -- Existing systems -- Note-taking -- Assumptions -- Meeting minutes -- Real-life scenarios with examples -- Scenario 1 -- Scenario 2 -- Scenario 3 -- Practical tips for success -- Summary -- Questions -- Further reading -- Chapter 2: Elicitation and Document Requirements -- Elicitation planning -- Elicitation tasks -- Requirement elicitation techniques -- Observation -- Brainstorming -- Surveys -- Interviews / focus groups -- Conference room pilots / requirements workshops -- Prototyping -- Process models -- User stories
|
| 505 |
0 |
|
|a Functional requirements -- Non-functional requirements -- Learning what level of detail is sufficient -- Requirements matrix (prioritized product backlog) -- Explaining a typical business requirement document and its key attributes -- Practical tips for success -- Summary -- Questions -- Further reading -- Part 2: Design, Development, and Testing -- Iterative Cycles with Prototypes and Conference Room Pilots -- Chapter 6: Solution Design and Functional Document -- Understanding solution design -- Identifying functional requirements -- Identifying non-functional requirements
|
| 505 |
0 |
|
|a Intro -- Title Page -- Copyright and Credits -- Contributors -- About the reviewers -- Table of Contents -- Preface -- Part 1: Planning and Analysis -- BRD/Prioritized Product Backlog -- Chapter 1: Identifying Requirements -- The role of business analysis in identifying requirement sources -- Types of requirements -- Securing support from the project sponsor -- Common sources where you can identify business requirements -- Document analysis -- Identify key stakeholders -- Navigate the organization -- Current system usage -- Identify the key end user -- Needs decomposition
|
| 505 |
0 |
|
|a Understanding and capturing the current state "as-is" -- Current state swim lane process flow diagram -- Proven techniques to capture the current state -- Identifying gaps and improvement/automation opportunities -- Developing the future state -- "to-be" -- Future state swim lane process flow diagram -- Benefits of creating process flows -- Summary -- Questions -- Further reading -- Chapter 5: Business Requirements Document -- Reviewing the need for business requirements documentation -- Understanding user requirements and use cases -- Exploring functional and non-functional requirements
|
| 653 |
|
|
|a Sciences de la gestion
|
| 653 |
|
|
|a Salesforce (Online service) / fast
|
| 653 |
|
|
|a Management science / http://id.loc.gov/authorities/subjects/sh85080363
|
| 653 |
|
|
|a Management science / fast
|
| 653 |
|
|
|a Salesforce (Serveur)
|
| 653 |
|
|
|a Salesforce (Online service) / http://id.loc.gov/authorities/subjects/sh2007004093
|
| 041 |
0 |
7 |
|a eng
|2 ISO 639-2
|
| 989 |
|
|
|b OREILLY
|a O'Reilly
|
| 015 |
|
|
|a GBC2I1983
|
| 776 |
|
|
|z 9781801813426
|
| 776 |
|
|
|z 9781801810579
|
| 856 |
4 |
0 |
|u https://learning.oreilly.com/library/view/~/9781801813426/?ar
|x Verlag
|3 Volltext
|
| 082 |
0 |
|
|a 658.8
|
| 082 |
0 |
|
|a 658
|
| 082 |
0 |
|
|a 500
|
| 520 |
|
|
|a Become a proficient Salesforce business analyst with the help of expert recommendations, techniques, best practices, and practical advice Purchase of the print or Kindle book includes a free eBook in the PDF format. Key Features Learn the intricacies and nuances of every stage of a project's implementation Discover real-world examples, tips, and tricks that you can apply to any Salesforce project Overcome the challenges inherent in user interaction and improve your customer experience Book Description Salesforce business analysis skills are in high demand, and there are scant resources to satisfy this demand. This practical guide for business analysts contains all the tools, techniques, and processes needed to create business value and improve user adoption. The Salesforce Business Analyst Handbook begins with the most crucial element of any business analysis activity: identifying business requirements.
|
| 520 |
|
|
|a What you will learn Create a roadmap to deliver a set of high-level requirements Prioritize requirements according to their business value Identify opportunities for improvement in process flows Communicate your solution design via conference room pilots Construct a requirements traceability matrix Conduct user acceptance tests and system integration tests Develop training artifacts so your customers can easily use your system Implement a post-production support model to retain your customers Who this book is for This book is for intermediate- to senior-level business analysts with a basic understanding of Salesforce CRM software or any CRM technology who want to learn proven business analysis techniques to set their business up for success
|
| 520 |
|
|
|a You'll learn how to use tacit business analysis and Salesforce system analysis skills to rank and stack all requirements as well as get buy-in from stakeholders. Once you understand the requirements, you'll work on transforming them into working software via prototyping, mockups, and wireframing. But what good is a product if the customer cannot use it? To help you achieve that, this book will discuss various testing strategies and show you how to tailor testing scenarios that align with business requirements documents. Toward the end, you'll find out how to create easy-to-use training material for your customers and focus on post-production support - one of the most critical phases. Your customers will stay with you if you support them when they need it! By the end of this Salesforce book, you'll be able to successfully navigate every phase of a project and confidently apply your new knowledge in your own Salesforce implementations.
|