1. Maintain margins
1.1. stronger review of scope and requirements
1.1.1. maybe have estimates done in two parts. initially just do a design review and then give an estimate for the development once we a better idea of what we are building
1.1.2. Break out discovery from ticket writing
1.2. Begin tracking actual impementation times in dev plans
2. Develop and promote industry thought leaders
2.1. Create a blog post publication cycle with demands of each department
2.2. host meetups
2.3. contribute to open source / open source internal tech
2.4. Internal Development Group
2.5. maybe an interactive office map would help to find each other and rooms
2.6. Tie thought leadership goals to senior and principal roles
3. Grow revenue
3.1. expand our drupal portfolio
3.2. rob bank downstairs
4. Increase number of services used by new/existing clients
4.1. Leverage AEM integration with other Adobe products, such as Marketing Cloud
4.2. Build tools/enhancements for clients in such a way that we can easily repackage and sell to other clients.
4.3. An Internal Development team can R&D or polish up client work to proof of concept offerings such as Mobile Apps or other offerings that could be added to our 'reusable assets'.
4.4. An Internal Development team can R&D or polish up client work to proof of concept offerings such as Mobile Apps or other offerings that could be added to our 'reusable assets'.
5. Strengthen the Velir Brand
5.1. Create new tech blog for quick dev posts.
5.2. Maybe a greater focus on Non-profit companies or industries that are of that nature (helping people)
5.3. Allow time for internal data visualization intiatives to showcase new technologies and increase awareness of Velir in the Data viz community
6. Expand service offerings
6.1. Automate website audits to the greatest extent possible. Use these tools on our own website builds
7. Retain existing accounts
7.1. Offer a discount on licenses if they sign up for support contract
7.2. Consider providing modules or upgrades of modules for free based on size or duration of account
8. Deliver a superior customer experience
8.1. Create a private area in Jira for Velir only comments
8.2. Polish the deliverables so things we present to clients always look good.
8.3. Develop websites with real content from the start of the project
8.4. Solve Design QA once and for all
8.5. Hit a 90% acceptance rate in UAT. Do not treat clients as a QA resource
9. Align delivery processes to customer needs
9.1. Eff those guys
9.2. try adopting a better MVP approach. build just what is need to create a production viable website first
9.3. Setup out internal development environments to match the live setups, if they are using a distributed environment make sure that the internal dev envrionments are also setup that way to avoid issues
9.4. Ensure the entire team interacts with the customer - WHILE MINIMIZING MEETINGS, be targeted
10. Improve consistency of delivery
10.1. Integrate Dev planning into Jira
10.2. Set and use performance budgets on all projects
10.2.1. Identify the things/trends that will destroy our performance budget
10.3. better consistency with gulp tasks on projects, especially with CI
10.4. Internal Sitecore site, an example of our current recommended technology stack. Using re-usable components.
10.5. Use automated tools to ensure all deliveries meet our standards (testing, code guidelines, comments)
10.5.1. Use automated browser testing framework (Selenium / CodedUI)
10.5.1.1. Craft Feature issues from a behavioral driven development mindset to help drive expected and testable outcomes
10.5.2. Use KPI profiling as part of our CI build process. Think nightly performance profiling, with reports on deltas between builds
10.6. Developers should review tickets BEFORE they are submitted to client for approval. This would cut back on risk and over-promising
10.6.1. To piggy back on this, have the devs more involved with the initial definitions of tickets/features to avoid gaps and set reasonable expectations
10.6.2. Have SAs write tickets in a consistent manner and written in such a way any developer new to the project can complete the task