ArchKatasCode/lead.html at master · tedneward/ArchKatasCode · GitHub

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
<!DOCTYPE html>
<html lang="en">
  <head>
    <meta charset="utf-8">
    <title>Architectural Katas: Practicing Architecture</title>
    <meta name="viewport" content="width=device-width, initial-scale=1.0">
    <meta name="description" content="">
    <meta name="author" content="">

    <!-- Le styles -->
    <link href="./css/bootstrap.css" rel="stylesheet">
    <style>
      body {
        padding-top: 60px;
        padding-bottom: 40px;
      }
      .sidebar-nav {
        padding: 9px 0;
      }
    </style>
    <link href="./css/bootstrap-responsive.css" rel="stylesheet">

    <!-- Le HTML5 shim, for IE6-8 support of HTML5 elements -->
    <!--[if lt IE 9]>
      <script src="//html5shim.googlecode.com/svn/trunk/html5.js"></script>
    <![endif]-->
  </head>

  <body>

    <div class="navbar navbar-fixed-top">
      <div class="navbar-inner">
        <div class="container-fluid">
          <a class="btn btn-navbar" data-toggle="collapse" data-target=".nav-collapse">
            <span class="icon-bar"></span>
            <span class="icon-bar"></span>
            <span class="icon-bar"></span>
          </a>
          <a class="brand" href="#">Architectural Katas</a>
          <div class="nav-collapse">
            <ul class="nav">
              <li><a href="index.html">Home</a></li>
              <li><a href="about.html">About</a></li>
              <li><a href="rules.html">Rules</a></li>
              <li><a href="contribute.html">Contribute</a></li>
              <li><a href="invite.html">Invite</a></li>
              <li class="active"><a href="lead.html">Lead</a></li>
              <li><a href="contact.html">Contact</a></li>
            </ul>
          </div>
        </div>
      </div>
    </div>

    <div class="container-fluid">
      <div class="row-fluid">
        <div class="span12">
          <div class="hero-unit">
            <h1>Lead</h1>
            <p>Being a Moderator for an architectural kata session isn't hard, but there are a
            couple of requirements that must be obeyed if the group is to have an optimal experience:</p>
            <ul>
            	<li><p><strong>You must have sat through a run of the architectural katas.</strong>
            	The reason for this rule is simple: it's far easier to see what the Moderator role
            	is like when you've seen it in action. Plus, that way you get a feel for what the
            	event is like, overall, and understand a bit more of the "vibe" behind it.</p></li>
            	<li><p><strong>You must be able to think on your feet.</strong> Let me be 100% honest
            	with you here: a large part of being the Moderator is answering the various "customer"
            	questions that come up, and the kata proposals don't help you a whole lot here--they're
            	deliberately written to be vague, offering up lots of room for flexibility and
            	interpretation. That means you, dear Moderator, have to be willing to make up answers
            	on the fly (and remember them later, during the Peer Review Phase!) when project teams
            	ask you questions you'd never considered before.</p></li>
            	<li><p><strong>You must be willing to facilitate.</strong> Part of the Moderator's
            	job is to keep the group moving along at a speedy clip, so all the project teams can
            	get their Peer Review Phase in before time expires. (This is something I keep hoping
            	I'll get better at, just for the record.) You also have to be willing to step in and
            	redirect conversation when it threatens to get out of hand, either because the group
            	is falling into the "you suck/I rock" Dichotomy, or because the group is debating a
            	particular point just a little too long. This requires a degree of diplomacy and
            	finesse and tact. Or else a really loud voice.</p></li>
            	<li><p><strong>Your group must come up with a new Kata for the site.</strong> The
            	katas will only be as interesting as the ones that are generated by the community,
            	so as a "licensing requirement", I ask that any group that runs the katas to wander
            	on over to the
              <a target="_blank" href="https://github.com/tedneward/ArchKatas">GitHub
              repository containing all the katas</a> and suggest a new Kata idea for possible
            	inclusion.</p></li>
            </ul>
            <p>Beyond this, you should have some development experience, and ideally you've spent at
            least a little time as a software architect, but I don't think that's absolutely necessary,
            to be honest.</p>
          </div>
        </div><!--/span-->
      </div><!--/row-->

      <hr>

      <footer>
        <p>&copy; Neward &amp; Associates 2012</p>
      </footer>

    </div><!--/.fluid-container-->

    <!-- Le javascript
    ================================================== -->
    <!-- Placed at the end of the document so the pages load faster -->
    <script src="./js/jquery-1.7.1.min.js"></script>
    <script src="./js/bootstrap-collapse.js"></script>

  </body>
</html>