Categories
Social Software

My Five Ws of IBM’s Lotus Greenhouse in less than 10 minutes

Use IBM’s Lotus Collaboration Products for free, including Lotus Connections for social networking.

Inside Registered Greenhouse

Who

I’ve been blogging, or, talking about IBM’s Lotus Greenhouse for a while now, but have yet to deliver a scenario that folks can relate to. So for all of you out there that have a desire to know more about social software and maybe even start testing the waters, this series of posts is for you.

Why

Most of my friends and colleagues think social software is limited to blogging. Some consider video sharing like youtube. Some know about bookmark sharing like delicious. Some may consider podcasts in there. Perhaps even fewer know about slideshare. I don’t know of any them that consider leaving comments on retailers’ site as being “social”. And again, none of them would consider some form of project management as a social activity.

Now, what’s nice about IBM’s Lotus Greenhouse is that it offers all of these capabilities and more, for free. Why? I can think of two good reasons why IBM let’s you use their production, backed-up software for free:

  1. Outside-in software development: There’s a big push within Big Blue to get more feedback from stakeholders outside the lab into the lab. Greenhouse has a whack of forums for members to provide feedback, or, get help. This goes hand-in-hand with another big push in Big Blue: Agile, or, scrum software development. In very brief terms, this means developing high value chunks of executable software in short iterations cycles – like two weeks, demonstrating it to stakeholders, getting feedback, reflecting on the experience & then moving forward. The objective is to mitigate the risk in developing software no one except the developers think is necessary. (Perhaps now’s a good time to point you to the Disclaimer on my sidebar.)
  2. As the site says:

    Bluehouse is the code name for a first-of-its-kind, IBM® software-as-a-service (SaaS) offering. “Bluehouse” is an innovative and powerfully intuitive set of business services integrated with robust social networking capabilities, which enable users to collaborate quickly and efficiently work with others outside or inside the firewall.

    So my guess is, if you get hooked on Greenhouse & are reaping the benefits from it, then you would consider going for the full-meal deal with the Bluehouse hosted solution. Makes sense to me!

What

Glancing at the Inside Greenhouse image above, you can tell there’s a lot going on here. But I did say in my last The Funny Thing About Leaving Comments post that I was going to use Chris Brogan‘s Question for You While Preparing for 2009 getting started scenario. So that’s what we’re going to focus on moving forward – for now.

Where/How

Join Now In order to move forward, you do need to register by clicking Join and filling out the Self Nomination page. Now there’s a few things you should be aware of when registering:

  1. You cannot change the following after you register:
    1. E-mail address
    2. First Name
    3. Last Name
  2. I honestly don’t know if it helps any of us, but I can’t imagine it could hurt, so, feel free to use my name as Your IBM Contact

The first point really tripped me up. As a result, I now have an account with my IBM email address, first & last name and another one with my stevenmilstein.com email address with first name “S” and last name “StevenMilstein”. I’m trying to get this resolved since I have more control over the fate of my stevenmilstein.com email address, as opposed to, my IBM one.

When

Registration is not automatic. I think there’s a human intervening on the other end. So the sooner you register the sooner you can get started.

Please let me know if you have any trouble following my instructions, or, hit a snafu along the way.

Categories
Social Software Startup Life

The Basis for a Social Experiment

Agile Social Software Compass
Agile Social Software Compass

Basis for my outside-in social software experiment, benefiting non-techies and the developers who write this stuff.

The Basis
In the spring of 2008, I read Outside-in Software Development: A Practical Approach to Building Successful Stakeholder-Based Products by John Sweitzer and Carl Kessler of IBM’s Software Group and having a software developer’s background myself, was truly inspired. So much so, that I reached out to Carl Kessler (one of the huge perks about being an IBM’er – we can do things like that) and asked him if he knew where I could gain some practical experience as a Product Owner with a team actually practicing outside-in agile software development. I was hooked up with a team in a matter of days and truly had a great experience.

The Social Aspect
Since then, I’ve spent a considerable amount of time following the Forward Thinkers on my sidebar to the right, as well as, a few of the books (under Pivotal Moments) they introduced me to. Pretty soon I noticed the connection between outside-in software development, the agile/scrum software development process and social software.

Without getting into the specifics of each, the one common thread shared by all was that true business value, or, success, could only be achieved when the community/tribe worked together to achieve their common goal.

The state of affairs
Now while I work for IBM, I don’t work for Lotus – the keepers of IBM’s social software, nor do I work in the brand of the VPs mentioned above. I’m not in sales, nor am I in marketing. Take a look at my brief About – I’m a business analyst in Rational. I have no sphere of influence on any of those other brands

The experiment
So what I’d like to do – with your help of course, is starting from outside of Big Blue, put together a simple scenario where we feel social software will provide true business value for all stakeholders concerned. And by Stakeholders, I mean you, me, and the community/tribe we assemble. Since I am outside the trusted firewall, have my Disclaimer in the Sidebar and am secure with our Business Conduct Guidelines, this tribe is not restricted to IBM’s software development community. Anyone from any software development community can become a stakeholder.

Defining success
Like any experiment, or, project, we need a deliverable – something that can be measured. Something that we as stakeholders can say defines success. Here’s my suggestion: We, as stakeholders, want to deploy a social network with a specific non-technical mandate, using IBM’s social software, so that we can achieve our goal while contributing to the greater outside-in social software development community.

Up Next
In the coming posts, I’ll describe the non-technical mandate I have in mind and then how we’re going to experiment with IBM’s latest social software offerings – for free, no obligations, no spam, no hardware required.

Until then, if you already have a simple, non-technical goal you’d like to achieve by implementing a social network, please let me know so we can compare notes.