CSM Early Bird Tickets On Sale!

Chris and Jeff will be leading another weekend Certified ScrumMaster class on September 11-12, and if you register before August 21, you can get you some earlybird pricing. And, to mix species metaphors, if you can muster being an eager beaver in addition to an early bird, and get yourself signed up for our newsletter before the next one goes out bright and early Wednesday morning (that’s the 11th), you can snag yourself a discount code for a significant additional discount.

Due to popular demand, we’re also working on scheduling a repeat of our popular Certified Scrum Product Owner class, so give us a shout if you’re interested in announcements for that class, too.

Posted in training | Leave a comment

ScrumMaster Shirt

Our friend Tami Blake, and her husband Larry, just designed this.

Protect the Team!

If you want it on a shirt, you can get it at their Zazzle site.

Fun!

Posted in ha ha funny | Leave a comment

East Coast Swing: Chris is heading for Maine and Connecticut next week

A string of training opportunities has Chris headed for the East Coast next week. Never one to sit alone in a hotel bar in the evening listening to guys who don’t look like George Clooney and girls who don’t look like Vera Farmiga compare frequent flier privileges, Chris will be speaking at a couple of local user groups during his trip, so if you’re on the East Coast, this is your chance to experience Agility California-style.

On July 12, Chris will be the guest presenter at the first-ever meeting of the newly-minted Portland Agile User Group. There will be free beer and a raffle that will include a half-off certificate to any Agile Learning Labs public workshop. (If you’re the lucky winner, we suggest the December 4-5 Certified ScrumMaster workshop–on the premise that you’ll be pining for some sunshine right about then.)

On July 14, Chris will be presenting at Agile Connecticut, in the Windsor area. Don’t know about free beer on this one, but both presentations will involve lots of fun and learning games–the TSA guys who go through Chris’ luggage probably think he’s a professional rodeo clown when they see the colorful supplies he carts with him.

Posted in events | Leave a comment

The Role of the First Follower

A couple of centuries ago, American independence was a movement. The idea caught on, and people were willing to make real sacrifices, because they believed in the movement. They believed that life would be better if the movement succeeded.

Do you believe that agile practices, such as Scrum, can make life at your company better? You’ll need to start a movement. Here’s a pattern: Attract a ‘first follower’ and treat them as an equal. Now, work together to build support. Remember, it’s not about you, it’s about the movement. Good luck!

Thanks to my friend David Chilcott for sending the video link to the BayAPLN email list.

Cheers,

Chris

Posted in agile | 2 Comments

User Stories and Pair Programming: Two Chances to See Us Tomorrow

Chris will be leading off the Agile Manager’s Support Group in San Mateo with a presentation on the theme, “Help! Our user stories are too big!” As usual, there will be a raffle and free pizza, and as a special bonus, you’ll get to take home a copy of our Agile Dictionary sampler, a booklet containing highlights from the new website.

Meanwhile, Steve Bockman and Rob Myers will be presenting on the theme, “Making Pair Programming and TDD Fun and Effective” at the San Francisco .NET Developers User Group‘s monthly meetup, which will be held at Microsoft’s Market Street offices.

Which one are you going to? Life’s all about making tough choices, isn’t it?

Posted in agile, support group | Leave a comment

Experiencing Agility at SD Forum

Chris will be giving a brief, experiential introduction to Agile on the morning of July 27, sponsored by SD Forum. For anyone who just wonders what the "fuss" is all about, this is a way to get a quick dose–not of lore and theory, but of what it might actually be like to live in an Agile world. One thing is for certain: there is no PowerPoint in this utopia. Also, if you're hesitating over whether or not to take the plunge and get your CSM, this is a good way to test drive Chris' material and teaching methods. This workshop will set you back a mere $35–$25 if you're an SD Forum member, and why wouldn't you be?

Posted in agile, training | Leave a comment

The Agile Dictionary: A is for Agile

Writing a dictionary turns out to be a fair piece of work. Who knew? We have had a soft launch this week, with Chris Sims handed out a hundred copies of a "sampler edition" at Agile Roots. And The Agile Dictionary now has a live website, with a handful of definitions, and counting. It is ready for your perusal and commentary at www.agiledictionary.com, where you can even sign up to get the Word of the Week delivered to your inbox. Don't think of it as spam, think of it as an entertaining diversion, something fun to read while you avoid answering all those other supposedly urgent emails.

Without further ado, here is an entry from the Dictionary:

Agile

An umbrella term for iterative, incremental software development
methodologies. Agile methodologies include Extreme Programming (XP),
Scrum, Crystal, Dynamic Systems Development Method (DSDM), Lean, and
Feature-Driven Development (FDD). Agile methodologies arose in
opposition to the traditional, phase-driven “Waterfall” development
method, which emphasizes top-down project management, “big design up
front,” silos for architecture and design, coding, and testing, and
extensive documentation. Agile methodologies share an emphasis on small
teams delivering small increments of working software with great
frequency while working in close collaboration with the customer and
adapting to changing requirements.

Etymology

The term “Agile” was first used by a group of Software pundits who
gathered at a ski lodge in Snowbird, Utah for the express purpose of
naming and defining the greater movement in which they deemed themselves
to all be participants. The original invitation to Snowbird went out to
those interested in “lightweight” development frameworks. The attendees
agreed that they didn’t like the negative connotations of that term,
and agreed to adopt the term “Agile.”

Posted in Agile Dictionary, agile | Leave a comment

The June Conference Circuit

If you're like us, you've dialed-back your conference-going in the past couple of years, but one event that's not to be missed is the Agile Roots Conference in Salt Lake City. Both Chris and Steve will be presenting, and we'll be handing out the very first "samplers" from our forthcoming Agile Dictionary project. Why do we love Agile Roots? Because it takes place in Salt Lake City, near the birthplace of the Agile Manifesto, and opens with a keynote address by Jeff Patton titled Nobody Wants Your Stupid Process. See, you want to go now, don't you?

Steve will be presenting one of Agile Learning Labs' greatest hits, a workshop he designed called Flying Through Bottlenecks. Chris will be doing The Great Agile Requirements Showdown, which could just as easily be called Showdown at the Agile Corral. Both workshops are participatory, and a lot of fun.

On the way to Agile Roots, Chris will be making a whistle-stop at the Better Software Conference in Las Vegas, where on Thursday, June 10th he'll do a little number he picked up from Steve, Eliminating Process Bottlenecks: The
Theory of Constraints
. I think I like Steve's workshop title a bit better, even though it's less explanatory; who doesn't want to learn to fly?)

Somewhere between the two conferences, Chris is going to manage to stop by Los Angeles to attend my son's high school graduation. What a whirlwind. Good thing he's so Agile….

Posted in agile, conferences | Leave a comment

The Agile Dictionary: E is for Extreme Programming

This is a sneak preview of an entry from Agile Learning Labs' newest publishing project, The Agile Dictionary.  Our mission: to craft succinct, state-of-practice definitions for common Agile terms, complete with origins and links to the most authoritative primary sources we can find for further information. We plan to beta test the definitions here on our blog, prior to publishing The Agile Dictionary 1.0 in print and online.

Many thanks to volunteers Angeline Tan and Tami Blake for their hard work as contributing editors, and to Jeff McKenna, who has bravely volunteered to serve as our first editorial advisor.

Extreme Programming (XP)

Definition:


An Agile software development methodology that emphasizes customer involvement, transparency, testing and
frequent delivery of working software.


The Extreme Programming canon includes a Customer Bill of Rights and a Developer Bill of Rights, and lists its core values as communication, simplicity, feedback, courage and respect. XP is a developer-centric methodology, and unlike Scrum, it prescribes specific coding practices like Pair Programming, in which two developers work side by side at a single machine, automated unit testing, and frequent integration. Another key
practice in XP is refactoring, or the continual improvement of design over many iterations.

 

The basic advantage of XP is that the whole process is visible and accountable. The developers will make concrete commitments about what they will accomplish, show concrete progress in the form of deployable software, and when a milestone is reached they will describe exactly what they did and how and why that differed
from the plan. This allows business-oriented people to make their own business commitments with confidence, to take advantage of opportunities as they arise,
and eliminate dead-ends quickly and cheaply. —
KentBeck

Read More »

Posted in Agile Dictionary | Leave a comment

Edistorm: online stickies with dot voting! Whee!

I'm just starting to play around with a really cool, freshly launched product called Edistorm, an online app that features draggable stickies and dot voting. It's a bit strangely positioned, as a consumer not a business product–the example in the tutorial is about cake baking–but beneath this surface is what looks like an extremely useful tool for distributed Agile teams who find themselves longing for the chaotic simplicity a sticky wall.

Stickies and dot voting are two of of our main tools here at Agile Learning Labs. Every free wall is a colorful mosaic, and I suspect we are putting at least one Post-It Note heir through college. Every retrospective (and we have a lot of 'em) ends in some form of dot voting, to narrow down our action items.

Why online?

Online stickies would in theory allow distributed teams to collaborating using the same format tools we prefer for co-located teams. The question then becomes, what makes real sticky notes so great, and do these benefits actually transfer to an online environment?

Big and visible

One benefit is that a wall of stickies serves as an information radiator. By virtue of being on a wall, they are always visible to the team–always on the fringes of  consciousness, accessible at a glance, without booting up or drilling through a menu. This benefit is lost by putting stickies online.

What's the alternative? Chris, Steve and I hold a remote stand-up every morning, looping Steve in via Skype video. We can just make out Steve's task board in the background, and he can just make out ours. It turns out not to matter too much that we can't read each other's stickies. We watch each other move through the task board, discussing each stickie as we move it from doing to done, or from the backlog to doing. We are happy with this set-up, and wouldn't switch to an online wall, as the benefit of having the information radiator outweighs the issue of legibility by a longshot. 

But that is a taskboard. I can see other situations in which Edistorm could be immensely useful for short-term uses, such as a distributed team retrospective, or brainstorming a small project, where you don't really plan to leave the wall up as a radiator anyway. And you could get creative about sharing, by projecting them on a conference room wall or
displaying them on a large monitor in each location.

It's Simple

One of our mantras at Agile Learning Labs is "What's the simplest thing
that could possibly work?" And about 50% of the time, the answer is
"sticky notes."

Write a sticky. Slap it on the wall. Move it around. Crumple it up and throw it away. That's pretty much all a sticky note can do. It is not programmable. And it is blissfully immune to feature creep.

Edistorm is simple now, but I'm not yet convinced that's by design. Right out of the gate there is a big red flag: it has already included a totally unnecessary feature, a "bot" that makes new "suggestions" based on your current set of stickies. The bot in the cake baking example in the tutorial creates stickies with words like "wedding" and "food" on them. You can turn the idiotic bot off, but my tender young mind should never
have been exposed to the existence of such a thing. How this could ever be anything but distracting and annoying mystifies me, and it tells me the company is in danger of loading its product up with bells and whistles that totally defeat the purpose of using stickies–i.e., to keep it simple.

That said, bot aside, the product really does work like a wall of stickies. It's simple, intuitive, and it just works. It is the dot voting equivalent of my favorite online task board, scrumy.com, which has kept itself ruthlessly simple in design.

If you want to see Edistorm in action, you can watch a nice, to-the-point tutorial, and if you sign up for a free trial, you can create a wall of your own, or visit a stickie wall the company has started where users can add to, or vote on, suggestions for improvements or new features.  Several bumptious lunatics have suggested things like a chat window, ven diagrams and Facebook integration. The only feature I voted for was to make the wall itself draggable, and to create an API–my thinking being that an API would encourage people who want to cruft the product up to do so on their own.

Speaking as someone who uses stickies and dot voting every single day, my advice to Edistorm would be to resist adding any feature that isn't also a feature of a real sticky wall. No chat windows, email, spreadsheet imports, etc. Let people who want that stuff use traditional project management software like Microsoft Project. Give me a virtual version of the real thing, and let me figure out how to use it, and what to use it for.

Posted in agile | 2 Comments