From fd49290d84a3a45572baa6e52a0f5bfe758eb663 Mon Sep 17 00:00:00 2001 From: Rob Harris <roharris@redhat.com> Date: Fri, 27 Apr 2018 13:54:32 +0200 Subject: [PATCH] Added monitoring intro --- exercises/6-return-of-the-app-monitoring/README.md | 6 ++---- 1 files changed, 2 insertions(+), 4 deletions(-) diff --git a/exercises/6-return-of-the-app-monitoring/README.md b/exercises/6-return-of-the-app-monitoring/README.md index 2f0d22f..6fec37a 100644 --- a/exercises/6-return-of-the-app-monitoring/README.md +++ b/exercises/6-return-of-the-app-monitoring/README.md @@ -5,10 +5,8 @@  ## Exercise Intro -Why do we use visual monitors? Gamification. -What are we doing in this exercise -_____ - +Why do we use visual monitors? Visual monitors support the tight feedback loop which is vital to an agile working environment. Being in a centrally visible location, visual monitors radiate information rapidly, meaning the team doesn't have to go looking for it. Visual monitors also provide a degree of accountibility while also keeping the team motivated to fix problems. With broken components visualised, seeing progress monitors change from red to green can give the collective feeling that progress is being made. Finally visual monitors can promote team cohesion as it enables all team members to be on the same page regarding the current project status. +____ ## Learning Outcomes As a learner you will be able to - Create dashboards in Jenkins to display build status -- Gitblit v1.9.3