We had a wonderful guest speaker (Patricia) who works as a product manager in CTG. She focused on teaching us about:
1. Knowing how to write a story/task.
The first thing when writing a task is to know what your design/functionality has to be-- you have to know what you are working on should do/has to do
CTG uses Sanity, a database that allows everyone to build sections and make updates (very user friendly); it helps tell developers what to expect
You should give background/context to the project that frames what you are doing and why
List exactly what needs to happen in the task/what the task needs to accomplish; examples are useful to explain
Acceptance criteria needs to be generated and will have a set of requirements before a solution is submitted for review
Scenarios can be included for additional specific instructions for issues with variations on the implementation and provide exact use cases
_2. Accessibility in development
Gives the ability for users with disabilities to be able to use a service using alternative tools and methods to get information to them; extremely important in dev right now
The 3 levels of accessibility are:
A- Basic needs/bare minimum
AA- Standard practice to have implemented into your apps (RBI strives for this)
AAA- Users with accessibility needs can have the same experience as any other user; this may require you to sacrifice UX and design
There are many different methods of implementing these features of accessibility
Today I Learned...
We had a wonderful guest speaker (Patricia) who works as a product manager in CTG. She focused on teaching us about:
1. Knowing how to write a story/task.
_2. Accessibility in development
(Sorry forgot to post this Friday!)