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 | |
Adilas Dev Mtg - 9.26.24.pptx | Doc/Presentation | 9/26/2024 | Slide show from Alan going over the 4D's (deficiencies) that we are seeing. It also shows some common cycles and how we plan on breaking those cycles based on more structure, processes, and virtual rules of sorts. Good stuff! |
Notes:
|
Developer meeting - We were calling it our "pause and pivot" meeting. I started out and we talked about some of the new development that we have done. There are some cool pieces and projects that have been pushed out recently. We then rolled into an MVP wish list for ship A (small project list that we would like to get done). We then talked about the crunch that we are in (financial and cash flow stuff). It's not super bad but we are struggling a bit. We have spent huge amounts on client acquisition stuff. Trying to make people happy. It gets super expensive. Alan did a small slide show and presented on some things. Alan did a great job. We had some open question and answer stuff. Dustin had some questions about maintenance budgets. See attached for Alan's PowerPoint. He started out with the 4D's, where we fail or fall short. We then talked about some cycles and how we plan on breaking those cycles. Steve talked to the guys for a bit and then we wrapped it up. Quote from Steve "What you think about, you bring about." Not sure where he got it, but I liked it. Basically, the plan is to pause and pivot, meaning, we will stop development projects for a bit until we can get caught up. The developers will do direct client work and custom code so as to relieve the burden from adilas. We are going to help them get projects and also help them with oversite, consulting, project management, and code sign-off. Another big goal that we have is to define ourselves a little bit more vs just going wherever the wind blow. This is both in people, roles, expectations, and development efforts. |