- list page
- detail page
- profile page
- dialogs to confirm
- dialogs with form information.
- Sign into the app (does not deliver value)
- Documenting all of the entities (does not deliver value)
- Metrics on entities documented triggering actions to remediate (delivers value)
- Assessing pass rate / fail rate / number of remediations to date (delivers value)
- Sign into the app (does not deliver value)
- Host an event (does not deliver value)
- Users sign up for event (does not deliver value) (could deliver value in that it shows trending or hype)
- Event happens and x amount of people attended (delivered value)
- Items like magic links for email authentication might be passing in development mode but failing in production. You should know the status of things in production. By some means. Whether by automated tests, manual tests, or process being a checklist that leads to manual testing.
A keystone is a central stone at the summit of an arch, locking the whole together. While a completed structure gives value serving some purpose. The keystone must exist first before the structure can be completed. Things that fit this mold are items like "Authentication / Authorization". Determining how to identify and ban bots from the platform / prevent bad actors.
While a completed structure gives value serving some purpose. The keystone must exist first before the structure can be completed. Things that fit this mold are items like "Authentication / Authorization". Determining how to identify and ban bots from the platform / prevent bad actors.
Here we get into design and the following two frameworks to evaluate a UI.
All of the meetings below are only effective if you continually re-evaluate does the meeting still provide value? No one wants to go to a pointless meeting even if they have an agenda.
pre-meeting agenda's can be fantastic to stay on task and extract value.
Just think, what were the characteristics of a good meeting? usually yourself and the other person had some goals going in and topics to discuss and in an effective meeting those items are discussed. Sometimes you make decisions sometimes you just gather information on the landscape. And sometimes you roll out information to the team or get information rolled out to yourself so you can align.
Routines encouraging synchronous time can be great! If there is nothing to discuss there is still value in everyone joining and then just dropping. It encourages the fact that you are there and available. Meetings encouraging synchronous time can help defer scheduling meetings or resolving issues to that time period protecting your focus. (This is sometimes known as batching.)
Standup - serves a purpose of showing up and synchrounous time
Retros - how do we get better this can be augmented well or replaced by an organized punchlist document of things we want to improve application wide.
Entrepreneural meetings - is what we are building actually useful. where are we now and where are we going?
Management meetings - what can we do to be more efficient in our current workflow? also do any tough convos need to happen 1 on 1 to see what motivates people and why they are here and if they are here long term or on the way out the door.
Technician meetings - implementation details of stuff soon to be worked. This could also be resolved post standup ad-hoc.
Standup meetings have been useful to me in my career in that they encourage accountability,they get you talking and dedicating a small time to an intended audience. I have found them to be a super power to the extent that I started having a daily standup about life with a few other friends. What are our goals in life. How are we progressing toward those goals (any steps in the right direction?) and are our goals and actions based in reality? If you want to be a musician but are unable to live off the earnings you should make an adjustment. Chatting with others helps that to be exposed and keeps you from malignant behavior. You would never play video games in a coffee shop with a peer hard at work sitting next to yourself (that social shame or respect of those around you can be as helpful as unplugging the tv).
I find meetings fascinating, it also should be noted I have very little meetings currently taking less than 1.5 hours of my time a day. more on meetings covered in this gist - link
Thinking about, "if you were promoted". What documents would you have appreciated that you could reach for "as needed"
SLO - service level objectives - The standards we aspire to have internally for other teams that consume our app and potentially for others. They also are loose targets and specific endpoints might fall outside of the parameters that you keep track of but do not necessarily fix. Tracking those items allows sessions where you make efforts to fix those issues in the platform. Scaling up as a bandaid behavior should be avoided.
SLA - service level agreements - Not a fan of these, they tend to be more rigid versions of SLO's that lead to lies and workarounds. Questioning the definition of how you measure how fast something is or other requirements listed in the document. Avoid lawyer speak at all costs.
Post Mordem - writeup of what happened as it went down and how to prevent it from happening again. Alongside this people should write a different document which are posts about great successes what happened and what went right.
Business plan and Mission statement - maybe valuable (could be situationaly helpful).
Swot analysis - maybe valuable (could be situationaly helpful).
Roadmap - probably containing items mentioned at the beginning of this document.
Make sure people align on vision however you want to do that. Okr's, Mission statement, 1 on 1's outlining what is the role of the member on the team. team level meetings outlining the role of our team. And what it would cost others in horse trading to loan out resources for the company good at the expense of the current teams goal.
Disclaimer, these were Random thoughts, non authoritative information (at present)