Problem
The problem I am addressing on this mission is that the close of a project could be any number. Issue 1 through 7 have to be the Session placeholders for the number index of the day of the week where 1 is Monday.
Solution
The solution that it's just too hard to remember anything complex, but we can remember the weekdays 1 through 7, future session, next session, project open, the project self, and project close, but anything else over complicates the system. I had though about adding Sessions A-L, but months later I couldn't remember which one was which. In order to even define what the self is we must open the project and issue 11 is good for this, no pun intended. If I can't remember the issue order then others certainly can't be expected to use the system.
It's important to document assumptions first about your customers, then develop personas so you can understand needs in order to identify requirements that govern abilities. Finally we must make changes and perform evaluations, and there inevitably will be incidents that arise and official publications. Finally every project needs a roadmap. Each of the former gets it's own issue ticket to create a bulleted list of items for each of the former collections.
- Session.Next.Monday
- Session.Next.Tuesday
- Session.Next.Wednesday
- Session.Next.Thursday
- Session.Next.Friday
- Session.Next.Saturday
- Session.Next.Sunday
- Session.Next.Weeks
- Session.Next
- Session.Future
- Project.Open
- This
- Project.Close
- Questions
- Hypothesis
- Personas
- Needs
- Requirements
- Abilities
- Value Propositions
- Use Cases
- Use Case Scenarios
- Changes
- Evaluations
- Incidents
- Publications
- Roadmap
- Corrections
File Affected
?
Problem
The problem I am addressing on this mission is that the close of a project could be any number. Issue 1 through 7 have to be the Session placeholders for the number index of the day of the week where 1 is Monday.
Solution
The solution that it's just too hard to remember anything complex, but we can remember the weekdays 1 through 7, future session, next session, project open, the project self, and project close, but anything else over complicates the system. I had though about adding Sessions A-L, but months later I couldn't remember which one was which. In order to even define what the self is we must open the project and issue 11 is good for this, no pun intended. If I can't remember the issue order then others certainly can't be expected to use the system.
It's important to document assumptions first about your customers, then develop personas so you can understand needs in order to identify requirements that govern abilities. Finally we must make changes and perform evaluations, and there inevitably will be incidents that arise and official publications. Finally every project needs a roadmap. Each of the former gets it's own issue ticket to create a bulleted list of items for each of the former collections.
File Affected
?