Join the DZone community and get the full member experience.Join For Free
Whatever new awaits you, begin it here. In an entirely reimagined Jira.
Okay, what I’ve done here is taken a practice that is necessary but lame and have tried to make it new and cool by slapping the word agile in front of it. You know, like agile modeling, agile development, agile analysis and agile DBA. But, really, this is more than just that … really.
Sometimes you have important meetings — such as department meetings or one-on-ones — that really can defy any form of standard agenda. One way to deal with these meetings is to run them in an organic, ad hoc fashion. The manager marks the start and end points of the meeting and people throw out and devour topics in between. That’s a bit chaotic and, in my opinion, inefficient. Another approach is to compile an agenda in advance of each meeting, where someone collects each discussion item via email, IM, hallway conversation or carrier pigeon and posts the agenda prior to each meeting. That’s a bit cumbersome and, quite frankly, medieval.
The agile agenda provides a simpler option, in just three steps:
- Prior to the start of the meeting, the manager writes “Agenda” on the whiteboard and adds underneath it any discussion items of which he or she is aware
- Meeting members call out any additional discussion items and those get added to the agenda. This can also be done more informally, where individuals add their own discussion items as they come in the door.
- The meeting starts. The manager or the group decides the order in which the items are discussed. People can add additional items to the agile agenda if they think of them during the meeting.
The meeting is over either when the group is through the agenda or the team has run out of time.
Published at DZone with permission of Peter Schuh , DZone MVB. See the original article here.
Opinions expressed by DZone contributors are their own.