AVIO Consulting has seen that our most successful MuleSoft clients are those that embrace best-in-class standards with both their MuleSoft practice and in their software development practice in general.
Our MuleSoft Maturity Assessment is a diagnostic tool for assessing your company's proficiency in five categories of the software development lifecycle. This 19 question survey is intended to be completed by a team and then reviewed with AVIO Consulting's staff.
Get Started
Fill in your personal details
Please complete all required fields
Next
1: Which option best describes your methodology approach?
Traditional or waterfall development
Some incremental development
Agile Methodology is standard
Please answer all questions
Next
2: Which option best describes the state of your functional and non-functional requirements prior to development?
1. Not enough or no clarity of the requirements
2. Evolving from 1 to 3
3. High level functional requirements are documented to some level of detail
4. Evolving from 3 to 5
5. High level functional and non functional requirements are documented along with the data mapping and the field formatting
Use the space below to explain your answer.
3: Which option best describes product ownership, documentation and approvals?
1. Documented requirements signed off rarely and may not have owner defined for all APIs
2. Evolving from 1 to 3
3. Documented requirements signed off often. Approvals are also documented
4. Evolving from 3 to 5
5. Product owner identified with clearly defined process for approvals. Documented requirements signed off and the approvals are documented.
Use the space below to explain your answer.
4: Which option best describes the security requirements of your company?
1. Security considerations are optional or not identified at the beginning
2. Evolving from 1 to 3
3. Security considerations are essential and part of the requirements most of the time
4. Evolving from 3 to 5
5. Security team is involved to provide documented feedback for API and underlying data. In some cases, security team sets the policies upfront and IT has to adhere to those policies.
Use the space below to explain your answer.
5: Which option best describes SLAs (service level agreements)?
1. No SLAs defined
2. Evolving from 1 to 3
3. SLAs are defined at high level
4. Evolving from 3 to 5
5. SLA requirements are clearly defined for every scenario with expected outcomes along with exception behaviors
Use the space below to explain your answer.
6: Which option best describes your use of test data?
1. Test data available sometimes or never
2. Evolving from 1 to 3
3. Test data available but not for all scenarios
4. Evolving from 3 to 5
5. Multiple set of test data available for all scenarios
Use the space below to explain your answer.
7: Which option best describes your practice of documenting decisions?
1. Decisions do not get documented
2. Evolving from 1 to 3
3. Decisions get documented sometimes but with little relevant information
4. Evolving from 3 to 5
5. Decisions are clearly documented including the reasoning and the personnel involved in the decision making along with the details of who approved
Use the space below to explain your answer.
Please answer all questions
Next
8: Which option best describes your defined integration patterns?
1. Few or zero integration patterns defined
2. Evolving from 1 to 3
3. Some integration patterns documented with defined criteria
4. Evolving from 3 to 5
5. Suitable Integration patterns documented with defined criteria along with the examples
Use the space below to explain your answer.
9: Which option best describes your practice of identifying and following best practices?
1. Very few or no best practices exist. Developers try to bypass best practices often or not enough checks exist to measure compliance.
2. Evolving from 1 to 3
3. Best practices are documented and enforced by manual checks
4. Evolving from 3 to 5
5. Best practices are documented and enforced by automated checks
Use the space below to explain your answer.
10: Which option best describes your code review request and approval process?
1. Policies exist but are often neglected or not considered
2. Evolving from 1 to 3
3. Manual reviews using a pre-defined checklist from best practices
4. Evolving from 3 to 5
5. Automated checks along with peer reviews using the checklist from best practices
Use the space below to explain your answer.
11: Which option best describes your design review and approval process?
1. RAML specs reviewed before the dev work sometimes. No SLAs defined.
2. Evolving from 1 to 3
3. Design gets reviewed along with the RAML specs before the dev work most of the time. Design also includes logical flow digram, sequence diagrams, API layers and definitions, security, non-functional requirements.
4. Evolving from 3 to 5
5. Identify common patterns, leverage traits. Design is updated as needed based on the feedback even before the development sprints.
Use the space below to explain your answer.
12: Which option best describes your approach to testing and code coverage?
1. Munits written for all flows including functional Munit
2. Evolving from 1 to 3
3. Munits written for all flows including functional Munit with code coverage of xx %. Explore the option of scripted/repeatable integration tests.
4. Evolving from 3 to 5
5. Munits written for all flows including functional Munit with code coverage of xx %. Explore the option of scripted/repetable integration tests. Implement scripted/reusable performance tests on deployed MuleSoft Apps.
Use the space below to explain your answer.
13: Which option best describes demos in your organization?
1. Demos are random or never happen
2. Evolving from 1 to 3
3. Defined scope of demo for every sprint
4. Evolving from 3 to 5
5. Defined scope of demo for every sprint with the right group to provide constructive feedback. Decisions and feedback are logged.
Use the space below to explain your answer.
Please answer all questions
Next
14: Which option best describes build and release pipelines in your organization?
1. Continous Integration - Pipelines exist to auto build and deploy to one non-prod environment
2. Evolving from 1 to 3
3. Continuous Delivery - Pipelines exist to auto build and deploy following the API lifecycle with manual approvals all the way to the production environment
4. Evolving from 3 to 5
5. Continuous Deployment - Pipelines exist to auto build and deploy following the API lifecycle with no manual approvals all the way to the production environment (when applicable)
Use the space below to explain your answer.
15: Which option best describes Anypoint Deployments in your organization?
1. Basic deployments to ARM and Cloudhub manually
2. Evolving from 1 to 3
3. Automating policy migration in API manager
4. Evolving from 3 to 5
5. Custom deployment process using API's to avoid any manual intervention. Automate other dependencies like client contracts, MQ, DB scripts and API policies.
Use the space below to explain your answer.
Please answer all questions
Next
16: Which option best describes your approach to monitoring?
1. No dashboards / Manual checks
2. Evolving from 1 to 3
3. Generic dashboards with API statistics
4. Evolving from 3 to 5
5. Custom dashboards through third party tools or by using MuleSoft Anypoint Monitoring to help support teams to monitor and analyze the platform/application resource usage and stats
Use the space below to explain your answer.
17: Which option best describes your approach to traceability?
1. Manually going through application logs
2. Evolving from 1 to 3
3. Basic dashboards provide the number of transactions in a given period
4. Evolving from 3 to 5
5. Ability to trace a particular transaction easily with status palatable to production support and business users. Custom dashboards as needed for business process that empowers the business teams with meaningful messages.
Use the space below to explain your answer.
18: Which option best describes your organization's use of runbooks?
1. Readme with some detail around what the application does and how it relates to business processes
2. Evolving from 1 to 3
3. Runbooks with some common troubleshooting steps and remediation strategies. Readme is accessible and meaningful to business.
4. Evolving from 3 to 5
5. Runbooks are part of the development process and are updated regularly. For example: Operations Procedure Runbooks (when applicable) - Documents to walk through the infrastructure support like patch applications, VPN tunnel modifications, firewall configurations, etc.; Application Troubleshooting - Documentation of different messages for each application and the steps to be taken for each of those messages.
Use the space below to explain your answer.
19: Which option best describes your organization's use of alerts?
1. Basic alert capabilities but within the application
2. Evolving from 1 to 3
3. Alerts configured within the application and also at the platform level
4. Evolving from 3 to 5
5. Alerts configured within the application and also at the platform level. Custom alerts defined for every use case to help support teams with identified primary keys to trace a transaction. Integrating alerts with slack messages or service desk tickets along with email notifications.
Use the space below to explain your answer.
Please answer all questions
Submit my responses
Thank you for taking time to fill out the MuleSoft Maturity Assessment. We will contact you after compiling your organization's results.
Return to home page