working on fixing bugs and then hoped on meeting with cory, kelly and steve

Fixing a bug where mapped enterprise vendors disappear because the enterprise corp id is replaced by the transactional corp id in the mapping process.

Coding, meeting and planning for go live.

Coding/Bug Fixing

Planning with John, Wayne, Brandon, and Cory.  Coding/Bug Fixing.

Coding/Bug Fixing

Planning and meeting with Cory, Brandon, John and Wayne.  Bug fixes.

Testing

Coding, Testing and Bug Fixing

Coding, Testing and Bug Fixing

Coding, Testing and Bug Fixing

Coding, Testing and Bug Fixing

Coding and Bug Fixing

Coding and Bug Fixing

Coding and Bug Fixing

Coding and Bug Fixing

Coding and bug-fixing

Coding and bug-fixing

Coding, bug-fixing, and testing with Cory

Coding and bug-fixing

Testing, coding and bug fixing

Testing, coding, and bug fixes

Testing with Cory and bug fixing.

Coding/bug fixing

Coding/bug fixing

Coding/bug fixing

Coding/Bug Fixing

Coding and Bug Fixing

Coding/Bug Fixing

Coding/Bug Fixing

Coding, bug fixing and troubleshooting.

Coding, bug fixing and troubleshooting.

Coding, debugging and figuring out a way to deploy for iAnthus

Coding

Coding

Coding

Coding

Coding

Coding

Coding

Coding

Coding and repository fixes

Coding

Coding

Coding

Coding and working with Alan

Coding

Coding

Coding

Coding

Coding

Coding and working with Alan

Coding

Coding

Coding and working with Alan

Coding

Coding and working with Alan

Coding

Coding and meeting with Alan

Coding

Coding

Coding

Coding

Coding

Coding

Coding

Coding & working with Alan

Coding

Coding

Coding

Coding

Coding

Coding

Helping Steve and then meeting with Eric on the enterprise item catalog and some of his questions. See EOT # 9796 in the shop.

Coding

Coding

Coding and working with Alan

Re-writing UI to new look and feel

planning/looking at code trying to figure out best way to rework UI to change thumbnails

planning/coming up with a solution on how to allow thumbnails to be selected/changed.

review code changes made for gallery and tested.

finished building out image service on view part page to pull in images to gallery. Locked photo/media content if using enterprise images only. tested.

finished db update for settings and built out options to select and store settings in db. tested.

working on image settings

Coding

coding

Coding

Coding

Coding

Development

Coding

Coding

Coding

Coding

Coding and Meeting with Cory

Coding

Coding  and meeting with Alan

Coding

Coding

Coding

Coding

Coding

Coding

Coding

Coding

Coding

Coding

Coding

Coding

Meetings with Alan and Brandon and coding.

GoToMeeting session with Alan going over add/edit parts logic. See EOT # 9622 in the shop.

Coding

Coding

Coding

Coding

Coding

Coding

Coding

Coding

Coding

Coding

Goals for this last sprint - better direction, get a graphical scrum board, who was claiming what

- Alan - We added the Jira board to help with visual and where things are at.

- Eric - We were faster! We had a better understanding of the subject matter, less new things (testing), and we had better standups. He liked the Jira board and how much it helped. He also liked having his own little branch and being able to tie it to the Jira board. Enjoyed having the other guys at his disposal, ready to help. He would like to see us not try to solve the problems during standup. Do that after the main meeting. Almost think in rapid fire... type layout - quick overview of the team and the project without interruptions. Scheduling and making sure we have a plan and trying to be as consistent as possible. Possible quicker communications and responses. Eric would like to keep getting better and understand more about TestBox (testing). Really making sure that our testing really proves that things are working and in order. Request for some training and quick reference guide (something like that) dealing with testing, mocking, samples, and strategies.

- Bryan - He liked Jira and even was thinking about how we could tweak our own adilas system to help more with project management tasks. Appreciated tons of help from others. He is wanting a quick communication tool, as well. Overcoming personal rejections of programs and tech.

- Chuck - He thought that it went faster as well. He also liked using Jira. As a recommendation, if you move a card, maybe leave some notes and/or comments. Saying... "Assumptions have killed more soldiers than bullets." Communication, communication! Request for a small little SOP for naming conventions and such. He also put in a vote for some sort of communication tool.

- Wayne - Thumbs up to the whole team. Request for more UML diagrams and helping us see the bigger picture, even how different branches mix and blend. Jira can do more than just sprint management. Maybe jump in deeper and use other tools there. Wayne voted on Discord for a communication channel.

- Alan - The team is becoming more comfortable, as a whole. Lots of roles, and lots of mixing and blending of those roles. More momentum from back or past sprints. The Jira board helped the team see things better. He liked the branch names matching the issue names on the board. This time around, there was a more constant push from start to finish vs just a big push at the start. The whole thing felt smoother. The transitions were better this time. Breaking down the user stories into smaller issues really helped. Being able to break things down smaller and smaller was helpful. Comments on code repo stuff (branches, merging, naming, and flow).

- Alan would like to see more options and tools for getting going once they (the devs) got stopped. Getting around roadblocks. Lots of options to use communication - notes, comments, emails, texts, Jira board, phone calls, meetings, chat, etc.

- Brandon - Shared some strategies for overcoming roadblocks.

- General comments - If it helps, let's look into it. Wayne is willing and able to help setup and manage a Discord server. Discord can do chat, video, voice, etc. Just for fun... the guys who have used Discord have done so via gaming. Good discussion about options. Wayne would like to create a developer user group on the adilas email server.

Eric - Finished up some stuff yesterday. Good to go.

Wayne - He did a pull and ended up with some problems. Needs some help from Alan.

Chuck - He got some links done and pushed up. Willing to help with code sign-off stuff.

Bryan - He was travelling.

Alan - He is going to be going over things in general.

Alan - Talking with Chuck about some missing links on one of the pages.

Bryan - He has some questions for Alan. Looking for his next piece.

Wayne - He is finishing things up and making progress. He has a few questions for Alan on some of the models and services.

Eric - Done with the enterprise DAO. Still needs some more help on testing. Possible case sensitive problems. Needs to work with Alan on integration tests.

Chuck - He did some code review and did some minor updates and fixes. He will be redoing the links on one of the pages.

Alan - Adding some new things to the Jira board. Leading the meeting.

Chuck - He got some pages done and is willing to help with code review.

Bryan - Working on some other year end projects. He is going to grab some other pieces. He will reach out to Alan for some help.

Wayne - He needs some more information on one of the pages. Generic functions vs super specific.

Eric - Travelling yesterday. He will be working on the enterprise service and then working on some DAO's (database access objects).

Wayne - Working on add and edit and action pages. Lots of work on the .cfm stuff. He is going to need some other code from the other guys (cross merging branches).

Eric - He has finished up the enterprise mapping service. He has also worked on both the UofM enterprise service and the part category service. His only block right now is the holiday work time (random). Eric said that things are going faster. That is good.

Bryan - He was travelling yesterday. He will be getting back on things in the next few days. He is being pulled off on some other projects. He may hold off on taking more right now, until he gets some of the other stuff done and finished.

Alan - Guiding the guys and making suggestions on timing and options. Helping to push the project further. Light refining of the goals and tasks that are needed.

Bryan - Making progress and needing some help from Alan

Wayne - Working on the action pages and full wire-up on the sprint one units of measurement.

Chuck - Finished up the add/edit part category page. Working on the category mapping page. Needs help with merging in files.

Alan - Light training on bit bucket, pull requests, and helping with code sign-off.

Wayne - Still working on some sprint 1 stuff for the unit of measure.

Bryan - Worked with Alan on the build model. Still learning some of this stuff. Not sure what is still needed. He wants to work with Alan.

Alan - Trying to help us (the team) be more accountable. Trying to help push the team more.

Eric - Adapting and refactoring our plan. Working on some services and trying to get things standardized. Working on a mapping service. Hoping to finish the enterprise mapping service.

Chuck - He got some mock-ups done for the part category pages.

Towards the end, there was quite a bit of talk about mocking things up, for normal code and for tests. We need the mock data for both. There was also some talk about test-based development.

Eric - Got his local up and working. Needs to be able to show debugging in ColdFusion but Docker is blocking that currently.

Chuck - Pushed up a new file and mock-up to Adobe cloud - XD file. After the discussion, he will make the new page into a tab interface to hide some of the web settings.

Bryan - Making cfc stubs. Started into the new model. Working with others on the parts that he is doing. He would like a little bit more help.

Wayne - Not much done yesterday. Took his name off of a couple of pages. He was working on case mismatches and helping developers with their local environment. He is going to finish up the add/edit unit of measurement page from a prior sprint.

Alan - Looking at things with Chuck on the layout of the add/edit part category page. New layout and some small tweaks to how the page looks and shows the info.

New sprint on the enterprise part category project. First standup for this sprint.

Eric - Planning on getting with Wayne and also working on his local environment. Has a Docker issue.

Chuck - Planning on working on the new pages, layout, and such. Questions on some branching stuff.

Bryan - Claimed a few pieces. Doing some research. Dealing with some new stuff.

Wayne - He was not there, on the meeting, but he claimed the action pages.

Alan - Was leading the guys. Light training on git and branches.

Cory - Had a question, who is going to fully integrate things and clean things up? Alan was going to finish some stuff up.

Alan - Talking about a bug backlog. These are things that have been pushed but known bugs still exist. He was doing some review and asking questions to some of the developers. Alan was bringing up bottlenecks and risk factors (single level knowledge or skills to do certain things). Alan and John were talking about the teams and who will do what. This may lead into more cross training and redundancy within our teams. Alan was taking some of his own notes as well.

John - He wrote an email earlier in the week. He is trying to help bring in some better management skills and style to the whole team. As part of the sprint, he wanted to help with the testing but got pulled into helping out with the wire-up. We are seeing a need for a middle level developer. Someone who can look at the frontend, understand it, and also be able to tie things into backend development pieces. Someone who can bridge the gap.

John would like to take some of his knowledge (from school and other work experiences) and keep expanding upon this. He also wanted to make sure that the project requirements and prerequisites were lined out better. He also wanted to be able to line up personal goals and sprint goals, to find fulfillment in the sprint.

John loves SOP's, standard places or documents, checklists, and step-by-step guides. Being able to repeat and duplicate things instead of inventing everything on the fly (aka faking it). There may be a growing need for more internal team training so that we can all do a number of different tasks.

Bryan - His role has been to take what has been done and tweak it going forward. Lots of single projects where he does all of the facets of the project. Different working with teams and diving up the tasks (frontend, backend, testing, integration, etc.) Still a challenge learning script and tags. Big challenge, but there is a pretty steep learning curve. He is enjoying what he has been learning. We are just now tipping the surface of what is possible and where we are headed. Keep making small changes and focus on one thing at a time (little percentages).

Chuck - He has really enjoyed working with the different teams and such. Keep working on better communication and direction. Email may not be hitting the mark. Wanting to be able to visualize and interact with the project and scrum board. A more standard and centralized approach - similar to Jira and Trello.

Eric - We are improving on teamwork and helping each other. We are striving to become a better team, working together. We got it done (minus some light clean-up that Alan will do). We lacked on our definition of "done". It wasn't super clear, and we didn't have a tight definition to compare or check against. He loves processes and going through the list (virtual checklist). Helping our, internal, processes be more tuned. What is done, what is our plan, what are the backlog pieces?

He was talking about the value of the standup and then making a plan, as a group. Realigning daily. Eric was expressing that we may have fallen down on the sprint planning meeting. We may have planned our timeframe before we planned the sprint. That may be backward. The process is improvement and progression.

Small topic on risk - who is in charge of doing what?

Heroics - self vs a team - We have all tried to be the hero multiple times. We really need to keep focusing on being a part of the team. We are still looking for a leader, still all learning. Sometimes we have built up expectations on how this whole thing works. Eric really wants more direction (at least right now). We don't fully know what to do, all of the time. We will keep working on this.

Small line from John - Build the piece to fit the hole, not the hole around the piece.

Everybody knows that adilas is a unique company and team. If truth be known, we are all a bit random (added by Brandon - master of random). We will keep playing and figure it out and how it works with our team. The goal is to keep playing. One of our limits or pieces that is different is that we are not in person. We are a virtual team spread over multiple states and even countries and time zones.

Daily Scrum or standup - what you did, what's your plan for the day, any obstacles or problems?

Alan was reporting on what he is seeing. He loves the fact that we got more buy-in on this sprint. He knew that there were different teams and still trying to help expose the guys to different pieces. We had some good communication, but then we get rushed into doing the next step, even if we don't fully know what that is. As a fun side note, even though we kinda got lost, we rallied and got it done. As we learn our skills, hopefully we will become more productive and self-governing.

If we have other big projects and pushes, we need to do one at a time. We had both John and Wayne out in the weeds for hours (days). There was some mixing within branches and projects. It complicated our sprint, this time.

No one likes to be the bottleneck. We've all been there. No fun, major unseen pressure. We are leaning towards hope and optimism.

Brandon - Heros or trying to be a hero causes burnout. I've played that role and been burned-out many times.

Cory - Keep moving forward and adapt it to our own needs. Pick and choose the strong points and key off of those. Busy enough but not too busy. Super fine line. For the team, keep chiming in and providing feedback and ideas.

Eric - Use those daily scums and adjust accordingly.

Alan - We need to visually depict the scrum board better. That seems to be a big need. Alan also sees that he may need to help give some directions on where to go/do next.

Alan - Showing off the mapping page. Showing some unit tests that he had written. Eric chimed in on some of the testing that they were running. Sometimes, backend testing helps a backend developer see progress because they aren't building new pages, forms, and seeing everything. He got into some of the code to show it to the others. Small talks on mocking the data (fake data to make it do certain things). Alan showed some lock-downs on the add/edit parts page.

Eric - Reporting on lots of first-time stuff, like testbox and unit tests. He did enjoy thinking through the testing logic. Fun to play with the different code level perspectives. Eventual library for future tests.

John - Possible two testing levels. Unit tests and integration tests. Alan was explaining that most backend stuff deals with unit tests. Often the frontend pieces tend to deal with the integration tests. Not always, but most times. John was feeling like he and Bryan were pushed into la-la-land on some of the page/integration testing. John was thinking that unit testing would be a better spot to start. He learned a lot, even about his local setup and environment.

Bryan - He felt like he was in la-la-land working with Wayne on some of the crazy testing stuff. Trying to get his head around mocking and faking the data. Bryan was looking for a visual example and then basing his work off of the example. It was a real challenge if he had to build it up from the ground up. He got a pretty good mix of frontend, backend, and testing.

Chuck - Showing the add/edit page. Switch to add or edit mode. Able to push up to transactional corps. Small facelifts on a number of pages.

Alan - Worked with Eric yesterday. Working on the action page - locked down the add/edit page, if the corp is a transactional corp. Currently passing all of the tests locally.

Eric - Worked with Alan yesterday. Plans to help with code review today. Wants to follow through with his naming conventions and make everything consistent.

Chuck - Got the two enterprise pages fixed and merged. Needs Alan's help for a quick fix.

Wayne - He and John were working on the action page. They have been busy with another huge release and putting out fires (changing the Application.cfm to Application.cfc stuff).

John - Still needs to work on the frontend forms. Working with Wayne. Wants to get Chuck to record some naming conventions and defaults. John really wanted the developers to know how to get to the docs and to really use them.

Alan was talking about code review and how we want to go about this. He wants to setup a peer type review and get another set of eyes on the code. If there are questions, we can add in comments and then have the original author review it. As a goal of the code review, it is not - I would have done it this or that way - it is more, does it work and can we understand it - great, a thousand ways to do something.

Notes from the GoToMeeting chat:
How to get to the adilas docs... classic homepage/maintenance/developer's homepage/view docs
Once on the docs, there is a menu on the top right corner, go to systems and adilas core - tons of info from there.
If you guys need or want, we will authorize up to 2 hours per person if you guys want to go in and look at and read the adilas docs - see instructions above. Use time id # 1559 to bill your time.

Bryan - Just checking in and reporting. He and Wayne are working on some clean-up. He needs to get with Wayne to figure out the next steps. Feeling kind of lost dealing with the higher script level pieces. If it is in tags, Bryan can do it. If it is in script, he has to wait for help.

Alan - Was reviewing the sprint backlog with the guys. Alan is going to work with Bryan to help push the ball forward.

John - Not really part of the sprint.

Eric - He was switching servers (CF 2016 to CF 2021). Still testing.

Chuck - He just got a multiple corporation environment setup this morning.

Wayne - Had a busy weekend. Not much done since Friday (currently it's Monday). Working on the unit test for the action page.

Alan - Working with Eric and working on testing and the database updates. We also talked about testing and how when you first start, it feels kinda crazy to test fake (mocked up) data, but it really does have a value over time. He will be working on the DAO's and a few new methods for the enterprise corporation model.

Eric - Sent an email for his update

Wayne - Talked about testing and the value of it. Showed a demo of the new interface from Chuck and some of the logic that they are doing and working on. Showing push to all and push to select. Once a mapping exists, keep it up to date (edit mode) automatically.

Bryan - enjoying working with Wayne. Got TestBox installed on his server. He and Wayne will be wiring up the frontend.

Chuck - He will keep working on a few things.

Some assignments were being made for the next steps. They (Alan and Wayne) also were going over the enterprise corporation model and some of the existing methods that are available to all pages and parts of the system.

Alan - Still working with Eric - Coordinating together

Bryan - They decided to take out a click and extra page and decided to get one less page in the process.

John - Having issues on his local - ColdFusion file/folder mapping issue

Eric - The standup is just for surfacing issues - balance of talk and time - standup is a quick lightweight meeting - who is held up and why?

Chuck - He was on a different project or path yesterday - expressed some confusion and frustration - wanting a more clear picture of what is needed and wanted

Alan created a new branch called "sprint_2_uofm".

Alan - He and Eric are going to work together to tweak out the enterprise model. They will do a service (part of) the bigger enterprise model. Planning some look and layout. Small explanation of some object notation. Eric chimed in a bit as well.

Wayne - He, John, and Bryan are transferring the user story into a unit test or unit tests. That will take a bit to get into that.

Brandon - I pushed up the video on the media/content for this element of time.

Chuck - He needs some help setting up the extra cops for his testing environment. Brandon will help there. He is working on some design changes.

In general, going over and refining some of the existing user stories and acceptance criteria.

Alan wanted to break things into two different levels:
- Page level - tags and html
-- Unit tests for the pages

- Object oriented land - cfscript
-- cfc's
-- Unit tests for the cfc's

Small Teams:
Eric and Alan
- Enterprise uofm object - methods, services, and dao's

Bryan and Wayne and John
- Enterprise push page and actions
- Practice mocking up and faking data
- ok to do it out of order

John - on the side - frontend - tags

Chuck - page level - facelifts - nav - flow

See the media/content for a 21 minute video on the enterprise unit of measure - recorded from our sprint planning meeting

The sprint for the UofM started on 11/15/21. The main branch name is "sprint_1_uofm".