Alex Atkinson AlexAtkinson

On Acceptance Criteria

🗒️ An excerpt from my good, ol' Jira Team Runbook.

Acceptance Criteria tactices are ever evolving, but this is a good skeleton to start from.

User story
Functional requirements
Link to design docs / supporting resources
Technical breakdown and analysis to identify infrastructure dependencies

CORS -- Just the edge knowledge

localhost

To set cookies on the localhost, either have a self signed cert setup (see refs), or exclude the 'secure', and 'sameSite' directives.

CORS

Be aware of:
forbidden headers

Modernization/Dockerization Hazards Enablement

Despite Digital Transformation and application modernization being well established practices, there are always unforeseen issues the creep up. This exceedingly truncated list of hazards will hopefully help identify some issues early.

💡 This is a companion to -- not a replacement for -- the decadeds of retrospective material that exists on the subject. While it's advisable to engage an outside consultancy if you're unfamiliar with the topic, tackling this list early can offset those costs as their runbook will contain similar content as they assess your application.

Resources

Here are a few vids that give more context to this issue.

Domain Names, DNS, and URLs for DevOps & Friends

Table of Contents

Scrum/SAFe/Basic Project Management

Project Management can be as simple or as complex as needed. If your project is you and a few highly-aligned folks in the same room then you might be able to make due with a whiteboard and some sticky-notes, but this doesn't scale. There's a lot of expertise involved in taking a project from sticky-notes to a scaled agile enterprise operating model, but the foundations of planning don't change. IE: If you want to dig for treasure, then you should plan to get a shovel to enable your success.

Aside: Discover Your Minimum Viable Operating Posture

Before you jump into executing your vision, start by discovering a your minimum viable operating posture (see also the concept of minimum virtuous products), as this dictates a large portion of your overall organizational structure and talent strategy. Getting this wrong is similar to getting software architecture wrong -- it's all dysfunction and d

	#!/bin/bash
	# ----------------------------------------------------------------------
	# /root/build_mesos-slave.sh
	# mesos-master auto-build
	#
	# ----------------------------------------------------------------------
	# Variables
	# ----------------------------------------------------------------------
	user="root"
	dir="/root"

	#!/bin/bash
	# ----------------------------------------------------------------------
	# /root/build_mesos-master.sh
	# mesos-master auto-build
	#
	# ----------------------------------------------------------------------
	# Variables
	# ----------------------------------------------------------------------
	user="root"
	dir="/root"


	#!/usr/bin/env bash
	# ----------------------------------------------------------------------------------------------------------------------
	#
	# make-ca-cert.sh
	#
	# SYNOPSIS
	# Creates a CA if one doesn't already exist, and installs it (debian).
	# Creats a server certificate (including wildcard SAN) signed by the CA.
	#

	# ----------------------------------------------------------------------
	# File: check_failover_dhcp.ps1
	# Description: NRPE Nagios Check for Windows Server 2012 DHCP Failover Servers
	# https://exchange.nagios.org/directory/Plugins/Network-Protocols/DHCP-and-BOOTP/Windows-2012-DHCP-Failover-and-Scope-Health-Check/details
	#
	# Checks: Failover State
	# Failover Mode
	# Scope State of Each Scope
	# Scope Statistics (PercentInUse) of Each Scope
	#