Part 2: Design, Development, and Testing – Iterative Cycles with Prototypes and Conference Room Pilots

In this part, you will learn about the next phase of the cycle – solution and technical design – where we will discuss prototyping, mock-ups, and wireframing the solution design, and use conference room pilots to socialize the output to stakeholders and SMEs and get their feedback iteratively, incorporating them in the solution. This part will help you learn tools, techniques, and methods that you can implement and incorporate to transform prioritized requirements into working system software. We will discuss various testing strategies and how to capture scenarios aligning to business requirement documents.

Some of the challenges that we see in most Salesforce projects will be discussed in this unit, along with methods to handle them.

We will address some of the key challenges faced during this phase:

• Stakeholders seeing the application for the first time after completion of the development phase rather than getting involved from the start
• Complicated design features and overloaded Salesforce user interfaces
• The ability to identify and understand elusive nonfunctional useability-related requirements that matter most for end user adoption
• Not planning or insufficient prototyping activities during different phases of projects
• Lacking conference room pilots and workshops
• Treating requirement traceability as a project artifact and not as an important tool for identifying test coverage

The following chapters will be covered under this part:

• Chapter 6, Solution Design and Functional Document
• Chapter 7, Demonstrate Functionality Using Prototypes
• Chapter 8, Exploring Conference Room Pilots
• Chapter 9, Technical and Quality Testing
• Chapter 10, Requirements Traceability Matrix