The Southland Technology Conference, the conference I went to Friday and Saturday of last week, is an annual conference sponsored by local quality assurance and project management groups (where “local” means Orange County, Los Angeles, and the Inland Empire). This is its ninth year. Last year, it was upgraded from a one day conference to a two day conference, and this year it was upgraded again, this time by getting more experienced speakers.
I think the PowerPoint slides for the speaker presentations will be up on the web site, so I won’t blog my notes straight, since some of them simply repeat things that will be on the slides.
Vendor descriptions: There were thirteen vendors. These broke down into several categories: the ones that provided software tools, the ones that provided people to do a particular job, and the ones that provided education or training (including UCI). The sponsoring organizations also all had tables in the vendor room.
Talks:
The first keynote address was Kevin Parikh, CEO of Avasant, with “Outsourcing in 2020: A Forward Looking Perspective.” Avasant is a management company, focused on outsourcing. “In 2020, organizations will ‘right-source’ to locations.” One slide showed the different countries’ specialties: Israel for high end software and learning systems, China for embedded software and hardware solutions, India for application outsourcing and ITO, BPO, and contact centers, etc. Near term prospects could be found in Ireland, Russia, the Philippines, Canada, and Mexico, and longer term prospects in South Africa, Poland, and several Latin American countries. In 2020, the Western world will be competing with new market entrants - India, China, and Brazil. In 2020, Software as a Service will become the predominant delivery model for the application industry (SaaS also showed up in other talks as a trend). The pace of outsourcing: IBM increased from 3000 in India to 7300 in India in three years. However, “In 2020 organizations will focus on business innovation and keep critical skills in house.”
For the first parallel track, I went to Paul Hodgetts, the CEO of Agile Logic, who talked about “The Keys to Success with Agile Processes - Lessons Learned and Best Practices.” First we got where Agile came from. Ad Hoc software development -> Activities -> Waterfall -> Spiral -> Iterative/Incremental -> Evolutionary -> Lean -> Agile. All Agile talks at some point wind up contrasting Agile with the Waterfall model. The Warerfall model is a traditional software development model where you go through certain stages - first Requirements, then Design, then Coding, then Testing, etc. You can have some variation in how you subdivide things, for different numbers of stages, but all of them assume that you’re supposed to have fully completed one stage before you move on to the next. Agile, in contrast, assumes that you have smaller cycles, where you come up with some kind of functional prototype of the features you’re supplying, and then you go through iterations where you keep refining what you want. You release in smaller increments, adapt to change, and your team is supposed to be working together in a collaborative way and continually improving your process. This particular Agile presentation focused a lot on Scrum, which is a particular way of implementing Agile (as opposed to, say, Extreme Programming, another way of implementing Agile that the speaker considered less broadly usable and more specific to particular kinds of environments). Scrum involves Daily Scrum meetings, 30 day sprints, and stories (which are sort of like subsets of use cases).
Next track: I went to Mike Sanders, PMP of Southern California Edison, who talked about “Advanced Multitasking, Do More, Work Less, Be Happy.” The talk began with a story about him driving down a highway while on two cell phone conference calls (separate cell phones, one Bluetooth in each ear), thinking about a presentation, and eating a banana - and thinking what a peak of multitasking he’d reached, and how he needed to tell the whole world about it. I couldn’t help thinking of the descriptions I’ve heard of mania - it wouldn’t have felt out of place for the next words to be, “and then I discovered lithium.” But of course the wild example was the set up about how to do multitasking wrong, how doing too many things at once means getting less done, being less happy, etc. Doing multitasking right involves knowing that you’re actually task switching, and stuff like taking time, when letting go of a task, to record where you are and any information you’ll need when picking up the task again. This talk was a participatory one, where we were encouraged to put aside our notebooks in favor of responding.
Second Friday keynote: Eddie Hartman, cofounder, Chief Technology Officer, and Chief Strategy Officer of LegalZoom, talked about the founding of that company, and “The things you have to do to get a company started vs. the things you have to do to make a company great.” The thing they did to get the company started was to be hungrier than everyone else, work long hours, and take process shortcuts (”planning is for dummies”). The thing they needed to do to keep the company working over the long haul was relearn the value of process.
Next track: I went to Cathy Moran, talking about “It’s Not Easy Being Green.” The session objective was to “Motivate and enable you to discuss ‘Green Wave’ opportunities.” We need to reduce emissions 20% below 1990 levels by 2020. As it stands we are borrowing money from China to buy oil from the Middle East to harm the environment. A state of the art or best practice scenario could dramatically reduce energy consumption, by 2012, from what it would be if current trends continued (cue visual graph showing energy consumption either continuing to rise or going down, depending on what practices you adopt). Various green choices were discussed, including turning computers off at night, high efficiency technologies, virtualization and server consolidation, recycling, etc.
Last track on Friday: I listened to Lois Zells, consultant, talking about “Is Agile QA an Oxymoron?” She makes much of her money as an expert witness in failed software litigation cases that wind up in court. Save for a few Y2K cases, all of these cases have involved iterative software development. The presentation discussed best practices for QA, and for Agile development, and how to avoid being one of those cases of failed software development.
More tomorrow.