:smile: Hi
I've moved all of the work items over from TFS to GitHub so Kim wouldn't have to do it. I'll train her on item management and markdown when next we meet.
If I can get to some good user stories, we can get moving.
Kim and I are meeting Tuesday at about 6:30 til ... to teach her how to document her epics/features/user stories on GitHub and manage the backlog. When we get our first batch of stories up there, we'll have a grooming session and get going -- assuming Dustin and I have the build environment completely in place by then!
Using Trello? Probably, once I get the PO further along the feature and story trail. She needs to add detail to the features and begin to flesh out some stories so we can create the story board. Kim is coming over tomorrow evening for a couple of hours to learn how to add issues to GitHub.
Sad thing is, I just got done teaching her how to work in TFS and then we found out we didn't want to use it. Too restrictive and painful.
None of these epics or features has been prioritized, either. Hoping to get some detail down and have a grooming session. Meanwhile, we're working on getting a job pushed from local compile to final deployment. Walking skeleton.
Right now, I have no inkling of the MVP, either. I don't know yet which features she'll want first.
Dustin, if you get a chance, take a look on the Medical epic's comment about how to create the dsl's for the domains in this application.
Just checked. That particular tool would end up costing $40/month to allow a team edit capability. Let me look for an alternative. I can add you as a viewer, but I'll have to do all of the editing for now.
You should have a link in your gmail inbox. The board called 'Intake' is intended to present a series of events that occur, in order, over time from left (earliest) to right (latest). I've arranged it such that 'optional' events (like OrganizationCreated) are not on the central line, but offset. Hope it makes sense.
Now for the color-coded cards: Orange is something that happens during the process...anything that we'll have to keep track of (usually by saving it to storage). The green DomainEvents are things that someone OUTSIDE of the intake process would like to know about. For example, when we finish all of the steps filling out the Intake form(s), we fire the event 'Intake Completed'. That way, any other software we create (like notifying the Vet Tech they have a new critter to visit), will pick up that event and send it's message.
We do it this way to keep the software in little chunks that is easy to maintain, simpler to write, and not impacted by changes in other parts of the system. It also allows other developers (in the future) to participate without running into one another.
Back to business: We've done the events that happen (normal and Domain). When we think we have all of those done, we'll define the Commands (blue) and drop them in this diagram. You'll note that the events are always written in past tense. Commands are present tense, so we'll have a Command named something like Create Organization Contact associated with the Organization Created event (see the diagram). This is a command that the software on the browser will send to our application (along with the info that defines an organization contact).
So, we have a piece of software on the web browser (Chrome, Internet Explorer, whatever) that the user can see and interact with that sends Commands to our hosted application. Those commands, after they are executed, fire these little Events that cause things to be saved, messages to be sent, etc. When we reach a point where anyone outside of the Intake process needs to be made aware that something happened, we send out a Domain Event.
Ok, I'm not going to feed you with a firehose any more. The next time we sit down together we'll talk about a few more things: Aggregates/Entities, Policy, External Systems, and Bounded Context. When we get through that you'll be a DDD (Domain-Driven Design) consultant! Yea!. Seriously, you'll be able to work with me on a equal level to define and understand how our software works. That's the important part.
The whole purpose of all of this stuff is so we can have clear communications when we work together. We'll actually create a specific language to talk about these things and it will make everything easier.
Oh, to answer your question, attach documents to their epic for now (AnimalRescue/AnimalRescue#4)
Linda, I have a specific question about this item: https://github.com/AnimalRescue/AnimalRescue/issues/10..should this be a rules-based decision like, "if the Intake type is 'surrendered stray' and animalType is 'Cat', then placeInIsolation = true?