From 8e79e9defb6f1d99785ab315a383e5ef96d25333 Mon Sep 17 00:00:00 2001 From: Brandon Burton Date: Fri, 7 Jul 2017 14:26:14 +0100 Subject: [PATCH 1/3] Create development pipeline guide --- development_pipeline.md | 50 +++++++++++++++++++++++++++++++++++++++++ 1 file changed, 50 insertions(+) create mode 100644 development_pipeline.md diff --git a/development_pipeline.md b/development_pipeline.md new file mode 100644 index 0000000..7ea3cbd --- /dev/null +++ b/development_pipeline.md @@ -0,0 +1,50 @@ +# Createk's Development Pipeline + +## Our approach to development + +Createk currently operates in a hybridized Kanban/Scrum fashion. What that +means is that while we don't appoint values to our tickets on the Kanban +board we still operate in two week sprint blocks + +During our Sprint meetings we'll: +- Start with a Retrospective where we review the previous sprint looking at +what went well, what could be better, and what actions we can take to improve +- Move tickets from our Backlog/Planning columns into Planning-Done. +- Discuss potentially problematic tickets; i.e. blockers to completion, potential +solutions +- Sometimes assign specific individuals to tickets if the tickets have a +particularly high priority; i.e. The tickets are part of a large feature with a +looming deadline where the developer has a good deal of experience + + + +### Step 1: Selection +- Select a ticket from the top of the Planning-Done column (these are +ranked by highest priority; descending) and assign yourself and anyone +else working on it with you + +### Step 2: Development +- Commit your changes. Be sure to push often to allow Circle to run your +newly added tests often to receive feedback from the test suite + +### Step 3: Review +- Create a pull request. Look over the checklist and get members of the team +to review your work. If the product owner is available try to +show them the completed work to make sure it meets their expectations + +### Step 4: Changes +- Make the requested changes, if there are any + +### Step 5: Merge +- Merge to Staging +- Start a new ticket + +### Step 6: Test +- Corporate Rewards manually tests on Staging + +### Step 7: Re-work +- Potential re-work (If necessary, stop work on your newly selected ticket and +complete the requested changes then move through steps 3 to 6 again) + +### Step 8: Deploy +-[See our Git workflow](http://github.com/CreatekIO/guidelines/blob/master/git_workflow.md) From 8019e1ce8b9e1125269f503091e3bdc982dce205 Mon Sep 17 00:00:00 2001 From: Brandon Burton Date: Fri, 7 Jul 2017 14:31:04 +0100 Subject: [PATCH 2/3] Text under Deploy should be bulleted --- development_pipeline.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/development_pipeline.md b/development_pipeline.md index 7ea3cbd..3bd66f8 100644 --- a/development_pipeline.md +++ b/development_pipeline.md @@ -47,4 +47,4 @@ show them the completed work to make sure it meets their expectations complete the requested changes then move through steps 3 to 6 again) ### Step 8: Deploy --[See our Git workflow](http://github.com/CreatekIO/guidelines/blob/master/git_workflow.md) +- [See our Git workflow](http://github.com/CreatekIO/guidelines/blob/master/git_workflow.md) From d8831e5ee245bf8fe179e791a12fb030a18efaa1 Mon Sep 17 00:00:00 2001 From: Brandon Burton Date: Fri, 7 Jul 2017 14:33:09 +0100 Subject: [PATCH 3/3] Text under Deploy should be bulleted...attempt 2 --- development_pipeline.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/development_pipeline.md b/development_pipeline.md index 3bd66f8..1204f3d 100644 --- a/development_pipeline.md +++ b/development_pipeline.md @@ -47,4 +47,4 @@ show them the completed work to make sure it meets their expectations complete the requested changes then move through steps 3 to 6 again) ### Step 8: Deploy -- [See our Git workflow](http://github.com/CreatekIO/guidelines/blob/master/git_workflow.md) +- See our [Git workflow](http://github.com/CreatekIO/guidelines/blob/master/git_workflow.md)