Jennifer Hamon jhamon

TLDR: The anchor is the maintainer of feedback loops within the team.

Encourage pivots to capture needed work as stories in the icebox.
Work with PM to prune and validate the necessity of stories.
Monitor and unblock story tracks that have been blocked for extended periods of time.
Keep an eye on the team’s velocity and monitor time spent on stories.
Be a conduit for feedback between the team and the PM, the team and leadership.
Check that the number of stories in flight match the number of pairs on the team.
Work with PM at pre-IPM to ensure work is well-defined.

I hereby claim:

I am jhamon on github.
I am jhamon (https://keybase.io/jhamon) on keybase.
I have a public key whose fingerprint is F189 0F22 6222 5BF5 C0CB 9914 FA65 6D95 B881 AF59

To claim this, I am signing this object:

	require 'date'

	# The goal of this script is to identify log lines with a long time interval
	# between log lines. Tune this by changing $seconds_between_log_lines

	$seconds_between_log_lines = 4

	$timestamp_regex = /\d+\-\d+\-\d+ \d+:\d+:\d+\.\d+/

	def get_time(log_line)

	#!/bin/bash

	set -e

	readonly LASTPASS_KEY_LABEL='ssh_private_key'

	function usage {
	echo 'Usage: '
	echo 'pivotal_login <lastpass username> [options...]'
	echo

	# We're going to introduce a resource-type for the acl-service: bind-permission
	# The urn for these bind-permission resources looks like: urn:bind-permission:{resource-type}/{resource-namespace}
	# --> This allows the user to creating a role binding to a role containing an entry that might
	# look like: urn:{resource-type}:/{resource-namespace}

	# We plan to update the acl-service proof of concept to ensure the caller of our api has access control entries
	# ("permission of permission") granting them permission to bind roles of a given type and resource. The acl-service
	# will find the userId in the bearer token accompanying the request to ensure they have the bind-permission
	# needed to perform the requested actions in the acl-service.

	# Define a new role called space_developer
	POST /roles
	{
	'name': 'space_developer',
	'resourceActionTemplates': [
	{
	'resource': 'urn:app:/{org-guid}/{space-guid}/*',
	'actions': ['read', 'create', 'delete', 'update', 'run']
	},
	{

	-- change member_id to user id
	SELECT g.displayName from groups g JOIN group_membership gm ON g.id=gm.group_id WHERE gm.member_id="a15d185f-630e-426b-9698-04ebffe8149b";

	-- See which migrations have been successfully applied and in what order
	select installed_rank,version,success from schema_version order by installed_rank