Kick Off - Configero will conduct a kick off meeting to begin the project.
Personas, input channels, timing, and the finest-grain details about relationships (i.e.Drawing upon hundreds of Salesforce deployments, Configero has developed a proven implementation lifecycle, which includes the following phases: Personas, input channels, timing, and some finer details about relationships Specific technology or product subset, illustrating a single business capability and supporting relationships product owners), technical stakeholders, delivery team membersīusiness capabilities and high-level product positioning product owners), some technical stakeholders (i.e. architects), some delivery team members (i.e. “Art of the possible", Digital transformation scenariosĪ single business capability solution overviewĪ business process in support of a single capabilityįine-grained detail about a single processīusiness and executive stakeholders, technical influencersīusiness and executive stakeholders, some technical stakeholders (i.e. Marketing, Strategy & Sales Diagram Levels Marketing, Strategy & Salesįor example templates, see Marketing, Strategy, & Sales Templates Key Characteristics
#SALESFORCE PROJECT MANAGEMENT TEMPLATE SOFTWARE#
The concept of using levels to convey different kinds of detail is common to many frameworks, including the C4 model which is used to visualize software architectures. Below, we look at what these levels mean for each diagram style.
Selecting the right level for your diagram helps you communicate with the right amount of detail, which means even highly complex diagrams can still be easy for a viewer to understand.Īs you move from Level 1 → Level 4 you zoom into greater levels of detail, finer granularity, and reduced surface area or scope. We use a concept of 'levels' to help separate different kinds of details into easy to choose categories. This is where diagram levels come into play. After that, you have to decide what kinds of details best support your purpose. Purpose: Help viewers understand an implementation or product-related technical detail.Īudience: Delivery Teams, Technical Stakeholders Diagram Levelsīeing clear about the intentions and audience for your diagram is an important first step. Purpose: Help viewers understand concepts or a vision for a solution.Īudience: Business & Executive Stakeholders, Technical Influencers Documentation & Implementation Below, you'll see an overview of the two styles for Salesforce diagrams: Documentation & Implementation, and Marketing, Strategy & Sales. Clarifying the intent of the diagram you're trying to create is a critical first step in creating something that will resonate with your intended audience. We categorize diagrams into two general styles, based on purpose and intended audience. It can be difficult to know what type of diagram best supports a given scenario, what kinds of data can and can't be shown in various diagrams, or what kinds of diagrams best communicate with different stakeholders. Most diagrams only convey meaning to a specific set of stakeholders, for a specific purpose. The resources provided here and in the links below will help you get started building your own diagrams with a predictable, standardized look and feel. We developed this guidance to empower everyone to build accurate and understandable Salesforce diagrams. Unfortunately, a single diagram typically cannot convey meaning to every possible stakeholder. Diagrams are also critical to empowering business stakeholders to make the right purchasing and technology choices. Diagrams help delivery teams stay aligned, by serving as a single source of truth about the realities of implementations and products.
Diagrams communicate ideas to many different kinds of stakeholders, with many different needs. Diagrams are a key part of architectural work.