3 things for consideration architecture / solutions
- Requirements
- Assumptions
- Restraints
WORK ITEM TEMPLATE
Requirement/User story: Desired business value if applicable: Details/scope [include any COPY or styles requirements if not explicitly clear/stated in the next item]: Design docs, images, source/link:
Pre-Code Consistency check [not reinventing the wheel or breaking app wide pattern]: • make sure these states/style patterns are the same, if desired to be (check with design), for all parts of the app. • Check for global reusable styles and components.
Q: What event(s) is (are) expected to trigger the "expansion" in each viewport mode/device?
Possible events: Here is a list of the possible UI events for reference: https://developer.mozilla.org/en-US/docs/Web/API/UI_Events
DESKTOP: MOBILE: Other specific sizes (note the px size for media query) like Tablet if applicable: BOTH:
Q: What are the expected states related to this user action [can also be stated as the how to "handle" user input & events]?
Are the CURRENT states to be changed at all if NOT new? If so, each item would be split in 2 columns. DEFAULT STATE: SUCCESS: LOADING STATE: ERRORS STATES/UNKNOWN: ACCESSIBILITY Requirements: Translation Considerations: Data Persistence Considerations [Refresh, session expiry, leave page/tab come back]: OTHER STATES [this should cover ALL edge cases even if stating to not worry* in certain cases]: NOTE: not all states will be applicable to certain components. State can refer to text, or visual cues/style.
CAUTIONS/GOTCHAs or related work worth mentioning:
DevSecOPs journal
JIRA ticket MIAN GOAL - is to provide a central hub of info for what work is to be done and what is DONE and what is success. The busines susually has some ivory tower nah man you are dev do what I say we don’t need to expalin our reasoins.
CODE - serves users -- bsuiness GAIN such and such
Who is the END consumer ? why value
Why is it my job to flush out a ticket fully My job is to write code or be the interpreter of tickets maybe that is my job Cross funtoinal teams effectiveness Each person wants createive wiggle room and not feel like a robot
why wold they NOT fully flush it out ? is that not their job - they disagree its their job and or they dont have the skill or time or both to do that. ? why would they not equally be touchign bases with the DEVE while writing hte ticket to show in depth diers to know just aliek a dev owudl reach out to know his side.. ? And not feel micro managed see bottom comments
Ticket language TIPs: Work with FA for how to make it universal for business and developer. Shoot for a balance precision, concise, simplicity and technical jargon.
What is "Done"? Or acceptance criteria See here https://www.productplan.com/glossary/acceptance-criteria/ Are the Acceptance Criteria testable? If so, what aspect of (automated) tests can be done by devs and what part by Quality Assurance for example.
OPTIONAL- ICS Principles Check [mainly ask just ONE or more of the principles and communication guide stuff]: Is this solution simple? Is there reason to being up something seemingly out of alignment.
RASCI [who can make decisions for what aspects or contact for who to turn for help]: Change Process: If anything above changes do this…. Who notates? What type of things are REQURIED to be notated?
*-there is something to be said for level of sophistication of the required solution. User expectations are important to manage so there can be something noted if not covered as to maybe future enhancement. This preplanning will prevent needless questions that always surely can come from each developers experience as to how something "should behave."
*-there is something to be said for level of sophistication of the required solution. User expectations are important to manage so there can be something noted if not covered as to maybe future enhancement. This pre planning will prevent needless questions that always surely can come from each developers experience as to how something "should behave"
Research [understand the issue]
Reproduce error: Conditions: Auto play Subtitles not showing up no audio
Not an issue (they show up as would be expected) : Surface duo -- worked iPhone Full video
Understand the native API inner workings: - Text tracks property https://developer.mozilla.org/en-US/docs/Web/API/HTMLMediaElement Returns list listed test tracks-
Understand what drives how text tracks loads if any of the below are related cause (a) Dimension size (mobile web/desktop etc. tablet) (b) Device brand or model (c) Phone OS settings or Browser settings (d) Browser
Consider if device related then List of minimum supported tech aka devices or browsers
Check multiple languages
Compare issue to code already in the code base for reuse or pattern compare Locate files for code plan architecture if needed.
Evaluate multiple possible solutions Pseudo code Cover edge cases
QA Check for related moving parts -- try to break in those cases Optimize - for maintainability or SOLID code length what QA again if Optimized with changes