18. •Nodes: Servers
•Environments: Groups of nodes (Dev/QA/Prod)
•Recipes: Describes the desired state of a node
•Cookbooks: Group of Recipes
•Roles: Group of Cookbooks (Web)
•Attribute: information about the current state of a node
18
Wednesday, August 21, 13
22. •Nodes: Servers
•Environments: Groups of
nodes (Dev/QA/Prod)
•Manifests: Describes the
desired state of a node
•Catalog: Group of Manifests
•Facts: information about the
current state of a node
22
Wednesday, August 21, 13
27. •Nodes: Minions
•Environments: Groups of nodes (Dev/QA/Prod)
•States: Describes the desired state of a node
•Grains: information about the current state of a node
27
Wednesday, August 21, 13
30. •Hosts: Servers
•Groups: Groups of Hosts
(Dev/QA/Prod)
•Play: Describes the desired
state of a Host.
•Playbook: Group of Plays
•Roles: Group of Hosts (Web)
•Facts: information about the
current state of a Host.
30
Wednesday, August 21, 13
58. Features In Progress Blocked Tabled Testing Complete
Feature A
Feature B
Feature C
51
KANBAN
Wednesday, August 21, 13
59. Features In Progress Blocked Tabled Testing Complete
Feature A
Feature B
Feature C
52
KANBAN
Wednesday, August 21, 13
60. Features In Progress Blocked Tabled Testing Complete
Feature A
Feature B
Feature C
Feature E
Feature D
52
KANBAN
Wednesday, August 21, 13
61. Features In Progress Blocked Tabled Testing Complete
Feature AFeature BFeature C
Feature E
Feature G
53
KANBAN
Wednesday, August 21, 13
62. Features In Progress Blocked Tabled Testing Complete
Feature AFeature BFeature C
Feature E
Feature D
Feature F
Feature G
53
KANBAN
Wednesday, August 21, 13
63. Features In Progress Blocked Tabled Testing Complete
Feature A
Feature B
Feature C
Feature E
Feature D
Feature F
Feature G
54
KANBAN
Wednesday, August 21, 13
64. Features In Progress Blocked Tabled Testing Complete
Feature A
Feature B
Feature C
Feature E
Feature D
Feature F
Feature G
Feature H
Feature I
54
KANBAN
Wednesday, August 21, 13
65. Features In Progress Blocked Tabled Testing Complete
Feature A
Feature B
Feature C
Feature EFeature D
Feature F
Feature G
Feature H
Feature I
55
KANBAN
Wednesday, August 21, 13
66. AGILE DEVELOPMENT
• Individuals and interactions over process and
tools
• Working software over comprehensive
documentation
• Customer collaboration over contract negotiation
• Responding to change over following a plan
56
Wednesday, August 21, 13
67. AGILE TEAMS
57
Traditional Teams AGILE Teams
Project Manager /
Team Lead
Servant Leader /
Facilitator
Self-Organized
Wednesday, August 21, 13
94. 75
•Someone emails one of us a post
•We read it and send it back to them for revisions.
Our process was terrible
Wednesday, August 21, 13
95. 75
•Someone emails one of us a post
•We read it and send it back to them for revisions.
•They rewrite it and send us a new file... via email.
Our process was terrible
Wednesday, August 21, 13
96. 75
•Someone emails one of us a post
•We read it and send it back to them for revisions.
•They rewrite it and send us a new file... via email.
•Round and round we go.
Our process was terrible
Wednesday, August 21, 13
97. 75
•Someone emails one of us a post
•We read it and send it back to them for revisions.
•They rewrite it and send us a new file... via email.
•Round and round we go.
•We email the finished article to our editor, Andrew.
Our process was terrible
Wednesday, August 21, 13
98. 75
•Someone emails one of us a post
•We read it and send it back to them for revisions.
•They rewrite it and send us a new file... via email.
•Round and round we go.
•We email the finished article to our editor, Andrew.
•Andrew emails us a different copy with his edits.
Our process was terrible
Wednesday, August 21, 13
99. 75
•Someone emails one of us a post
•We read it and send it back to them for revisions.
•They rewrite it and send us a new file... via email.
•Round and round we go.
•We email the finished article to our editor, Andrew.
•Andrew emails us a different copy with his edits.
•We copy/paste into WordPress and post.
Our process was terrible
Wednesday, August 21, 13
110. 83
•Someone forks our GitHub repo
Our new process is
awesome
Wednesday, August 21, 13
111. 83
•Someone forks our GitHub repo
•They write a post: rake new_post[‘Some post’]
Our new process is
awesome
Wednesday, August 21, 13
112. 83
•Someone forks our GitHub repo
•They write a post: rake new_post[‘Some post’]
•They submit a pull request to us.
Our new process is
awesome
Wednesday, August 21, 13
113. 83
•Someone forks our GitHub repo
•They write a post: rake new_post[‘Some post’]
•They submit a pull request to us.
•We revise it via a GitHub discussion
Our new process is
awesome
Wednesday, August 21, 13
114. 83
•Someone forks our GitHub repo
•They write a post: rake new_post[‘Some post’]
•They submit a pull request to us.
•We revise it via a GitHub discussion
•We merge the commit.
Our new process is
awesome
Wednesday, August 21, 13
115. 83
•Someone forks our GitHub repo
•They write a post: rake new_post[‘Some post’]
•They submit a pull request to us.
•We revise it via a GitHub discussion
•We merge the commit.
•DEPLOY!
Our new process is
awesome
Wednesday, August 21, 13
