|
| 1 | +--- |
| 2 | +title: "Preparing to launch your First Mendix App with Compass" |
| 3 | +linktitle: "Compass for Start" |
| 4 | +url: /developerportal/compass/ |
| 5 | +weight: 25 |
| 6 | +description: "Describes the Compass tool." |
| 7 | +--- |
| 8 | + |
| 9 | +{{% alert color="info" %}} This feature is currently available to participating customers. For more information, contact your Customer Service Manager. {{% /alert %}} |
| 10 | + |
| 11 | +## Introduction |
| 12 | + |
| 13 | +The [Compass](https://compass.home.mendix.com/) tool is available to teams who want to plan and streamline the implementation of their first Mendix app. It is part of an initiative to bring [Mendix Digital Execution](https://www.mendix.com/glossary/digital-execution/) to the Platform, and enables non-developer team members to help plan the milestones and goals of their Mendix implementation process. Program Owners (that is, the team members leading the implementation) can then monitor the progress through an intuitive visual interface, with the goal of successfully launching their first Mendix application. |
| 14 | + |
| 15 | +{{< figure src="/attachments/developerportal/compass/compass-home.png" alt="The home page of the Compass tool" >}} |
| 16 | + |
| 17 | +With the Compass tool, you can define your own vision of low-code and the apps that you want to build with Mendix, and then simplify their implementation by following a number of predefined best-practice milestones. Each of those milestones consists of action points which you can assign to members of your team for easy tracking. If required, you can also define additional tasks for each milestone. |
| 18 | + |
| 19 | +## Getting Started with Compass |
| 20 | + |
| 21 | +To enable Compass for your organization, contact your Mendix Customer Service Manager. |
| 22 | + |
| 23 | +{{% alert color="info" %}} |
| 24 | +Compass is a tool intended for organizations that want to launch their first Mendix application. Many of the milestones and tasks are geared towards beginners, so teams which have already created one or more Mendix apps are less likely to find them useful. |
| 25 | +{{% /alert %}} |
| 26 | + |
| 27 | +After Compass has been enabled for your organization, a user with the Program Owner role can define the launch date of your first app on the Compass home page, and invite team members to participate. |
| 28 | + |
| 29 | +### Inviting Team Members |
| 30 | + |
| 31 | +The Compass team involved in your Mendix implementation should include everyone that will help get Mendix implemented in your organization. This team is not the same as the app project team which will build the app itself, although for example a lead developer might be present in both. You can find out more about the team scope and responsibilities by perusing the action points in Compass. |
| 32 | + |
| 33 | +You can give members of the team access to Compass by performing the following steps: |
| 34 | + |
| 35 | +1. Log in to [Compass](https://compass.home.mendix.com/) as a user with the Program Owner role. |
| 36 | +2. In the left navigation menu, click **Access Management**. |
| 37 | +3. In the **Invite Members** window, enter the email address of the user that you want to invite, and specify their role in the project. |
| 38 | + |
| 39 | +{{% alert color="info" %}} |
| 40 | +The Program Owner role grants users access to invite other users. As a best practice, follow the principle of least privilege, and only assign this role to team members who are leading the implementation. |
| 41 | +{{% /alert %}} |
| 42 | + |
| 43 | +You can invite users who are already a part of your organization, but also external users, for example, from partner organizations. Their invitations are displayed in the **Pending Invitations** tab until accepted. |
| 44 | + |
| 45 | +{{< figure src="/attachments/developerportal/compass/invite.png" alt="A screenshot of the Invite Members window" >}} |
| 46 | + |
| 47 | +## Tracking Milestones and Action Points |
| 48 | + |
| 49 | +Milestones are key points in the implementation process that must be completed in order for the implementation to be successful. Each milestone consists of one or more action points which can be assigned to members of your team. For example, the **Introduction to Digital Execution with Mendix** milestone consists of action points such as exploring the Mendix Platform, or assigning the administrator of your Mendix app. |
| 50 | + |
| 51 | +{{< figure src="/attachments/developerportal/compass/milestones.png" alt="A screenshot of the Introduction to Digital Execution with Mendix milestone with some action points completed and others in progress" >}} |
| 52 | + |
| 53 | +The milestones are defined for you by Mendix, based on our [Digital Execution](https://www.mendix.com/glossary/digital-execution/) framework. They do not keep track of development milestones - their role is to walk you through the steps which you must complete before development can start. |
| 54 | + |
| 55 | +{{< figure src="/attachments/developerportal/compass/milestones-home.png" alt="The Milestones page, showing some completed and open milestones" >}} |
| 56 | + |
| 57 | +You can view and manage milestones by performing the following steps: |
| 58 | + |
| 59 | +1. In the **Program** section of the left navigation menu, click **Milestones**. |
| 60 | +2. Click on the milestone which you want to view. |
| 61 | +3. Click on an action point to view the details or assign an owner and deadline. |
| 62 | +4. If you are the owner of an action point, follow the on-screen instructions to complete it. |
| 63 | +5. To view all action points assigned to you, click **Program** > **My Action Points**. |
| 64 | + |
| 65 | +{{< figure src="/attachments/developerportal/compass/action-point.png" alt="An action point with instructions on how to complete it" >}} |
| 66 | + |
| 67 | +## Adding Tasks |
| 68 | + |
| 69 | +Milestones and action points are predefined by Mendix, but you can also add your own custom tasks associated with each milestone. |
| 70 | + |
| 71 | +You can view and manage tasks by performing the following steps: |
| 72 | + |
| 73 | +1. In the **Program** section of the left navigation menu, click **Tasks**. |
| 74 | +2. To add a new task, click **Add Task**, and then provide the following information: |
| 75 | + |
| 76 | + * **Name** - Required. An identifying name for the task. |
| 77 | + * **Status** - By default, new tasks are created with the status **To do**, but you can also mark them as already done. |
| 78 | + * **Description** - As a best practice, provide a detailed description, so that the person working on the task has sufficient information to complete it. |
| 79 | + * **Deadline** - The deadline of the task. |
| 80 | + * **Assigned to** - The team member who must complete the task. |
| 81 | + * **Milestone** - The milestone with which the task is associated. |
| 82 | + |
| 83 | +3. Click **Save**. |
| 84 | + |
| 85 | +The new task is displayed on the **Tasks** page, as well as on the milestone with which it is associated. |
| 86 | + |
| 87 | +## Defining your Vision and Goals |
| 88 | + |
| 89 | +As you work on the initial tasks of your implementation, you and your team should develop a shared vision of what low-code with Mendix means for your organization. Compass helps you define and support that vision on the **Vision and Goals** page. |
| 90 | + |
| 91 | +{{< figure src="/attachments/developerportal/compass/vision.png" alt="The Vision and Goals page showing a sample low-code vision and key result" >}} |
| 92 | + |
| 93 | +### Low-Code Vision |
| 94 | + |
| 95 | +The **Low-Code Vision** is your overall guiding principle for the implementation. Use it to briefly describe what low-code means for your organization, and what goal you are working towards. Keep the description brief, and use the **Area of Focus** section to define the specifics. |
| 96 | + |
| 97 | +{{% alert color="info" %}} |
| 98 | +As a best practice, it can be helpful to organize a workshop with your team, so that you can brainstorm your low-code vision together. |
| 99 | +{{% /alert %}} |
| 100 | + |
| 101 | +### Area of Focus |
| 102 | + |
| 103 | +The **Area of Focus** section lists the following topics to plan for and consider as part of your goal-setting. |
| 104 | + |
| 105 | +* **People** - Goals associated with your team. For example, you may decide that you need to train five Mendix developers within the next three months. |
| 106 | +* **Platform** - Goals to integrate Mendix into your software development lifecycle. |
| 107 | +* **Portfolio** - The offerings where low-code can bring high value to your organization. |
| 108 | +* **Process** - Goals associated with your business processes. For example, you may decide to implement scrum. |
| 109 | +* **Promotion** - Goals to help you celebrate your successes and motivate your team to build with Mendix. |
| 110 | + |
| 111 | +These focus areas are based on the [5 Ps of digital transformation](https://www.mendix.com/glossary/digital-execution/#what-are-the-5-ps-of-digital-transformation). You can define your own measurable key results for each of those areas. |
| 112 | + |
| 113 | +{{% alert color="info" %}} |
| 114 | +As a best practice, key results should be granular and measurable in the short term. |
| 115 | +{{% /alert %}} |
| 116 | + |
| 117 | +#### Managing your Key Results |
| 118 | + |
| 119 | +To give your team transparency into the progress of your Mendix implementation, make sure to track the progress of your key results. You can do this by editing the value in the **Progress** field of a key result. |
| 120 | + |
| 121 | +{{< figure src="/attachments/developerportal/compass/key-result.png" alt="Tracking the progress of a key result" >}} |
| 122 | + |
| 123 | +## Read More |
| 124 | + |
| 125 | +* [Portfolio Management](/developerportal/portfolio-management/) - Another Digital Execution tool, geared towards pre-implementation strategic planning |
0 commit comments