Basic Assignments
|
Options & Settings
|
Main Time Information
|
||||||||||||||||||||||||||||
|
|
|
|
Sorry, no photos available for this element of time.
|
|
Uploaded Media/Content & Other Files
(1)
|
||||
Media Name | File Type | Date | Description | |
TeamCommentsSummary.docx | Doc/Text | 2/9/2021 | Working on question 23, where do we see Adilas in 1, 5, 10 years. We had some good discussion and made a bulleted list of goals that we thought was great. |
Notes:
|
Working with Shannon on vision statements and general goals for the next 1 year, 5 years, upto 10 years. See attached for our progress. Here is a list of some of our semi-short term goals that we will be adding to our business plan and vision plan: Without going into too many details here are some elements that will be included in our plan: - Keep tweaking on the transactional core - Move client services more internal to Adilas - Expand into other verticals - Allow for custom code where needed - Get into aggregated and/or business intelligence (BI) type levels - Grow the platform into an enterprise level app/system - Along the way there are plans to do a full re-write under the code name “Fracture” - Revamp the look and feel - improve user experience - Create and facilitate the Adilas Café and community /////////////////// We also talked about using the key word "core" for different starting spots or base level options. This could be core transactional systems, core database columns or fields, core or main pieces. An example may be something like: Using the word or phase core values vs parent attributes, sub attributes, flex attributes, etc. Hopefully that makes sense. Prepping things and doing some pioneering. All part of the game. At the end of the meeting, I ended up pushing up some code for Danny and his custom labels. |