We have 5286 guests and 8 members online
Home > Articles > Current Edition > Agile in the Mainstream

Agile in the Mainstream

E-mail
Tuesday, 09 August 2011 00:00
 
Agile in the Mainstream - August 2011

CoverIn agile, we encourage change. And, we certainly have change, now. In light of SQE’s acquisition of the Agile Journal earlier this year, we are changing our approach to the Agile Journal, aligning it more with our other communities. Part of that shift is initiating a more rigorous editing process and instead of one person doing it all, as our very own agile buddy Russell Pannone did, the work will be split between several people. I'll be working as the technical editor for the Agile Journal and copyediting and production work will be done by others, but no one could possibly fill Russell's shoes. He deserves our recognition and gratitude—thank you, Russell.

The topic for this month is Agile in the Mainstream. We have "Pair Programming in the Clink" by Daryl Kulak, a fascinating look at what happens when you volunteer to pair program in prison for a day. I read this article, and kept saying, "Wow, wow, wow."

I certainly agree with Len Whitmore's conclusions about "Agile Leadership for Mid-managers." But, what do you think?

In the "Plight of Product Owners in Medium and Large Organizations," Anupam Kundu highlights problems we've seen when organizations transition from one kind of organization to another. Have you lived through this transition? Have you seen it?

Delivering high-valued product needs is a goal on most if not all projects. Meeting this goal requires strong business analysis skills—a role not defined on Scrum teams. In "It's the Goal, Not the Role," Ellen Gottesdiener and Mary Gorman explain how to get your analysis needs met on these agile projects.

And, finally, teams testing the agile waters usually aren't in a position to hire a full-time ScrumMaster. But this role is essential to successful Scrum projects. In "Mission Possible: ScrumMaster and Technical Contributor," Steve Berczuk identifies some common issues teams face when trying to combine the responsibilities of a ScrumMaster with another role.

I hope you enjoy this month's Agile Journal.

And, again, I thank Russell for his years of devotion to the Agile Journal. Without you, Russell, we would not have the opportunity for change.

Johanna Rothman
Technical Editor
Agile Journal


 
Featured articles...

Pair Programming in the Clink
by Daryl Kulak 

A few weeks ago, I joined a crew of developers who traveled to Marion, Ohio, to participate in the unique experience of pair programming in prison.

The main purpose of this pair programming exercise is to help prisoners learn the art and science of agile software development. The idea is that you take several qualified developers from the outside world, get them into the prison for a Saturday, work on some exercises together with the prisoners, and everybody learns. It's like a code retreat, except it's inside a prison.

Read More >>
 

Agile Leadership for Mid-managers
by Len Whitmore

This theme of Agile in the Mainstream is interesting. If you search for it on the Internet, you find articles by Forrester and CIO with statistics that show X percentage of organizations do agile software development. While impressive, a more pertinent indicator that agile is in the mainstream is the revolutionary changes going on in organizations' management practices, with the agile movement being a major factor in causing these changes.

Read More >>
 

Plight of Product Owners in Medium and Large Organizations
by Anupam Kundu

Product owners in large organizations seem to have everything: the talented workforce, thicker wallets, well-recognized brand value, and the infrastructure to turn a seemingly common-sense idea into a spectacular business. Yet, they struggle to find the next innovative product that will create new markets and ecosystems. Is there something wrong with them? What prevents them from functioning like product owners in start-up companies who quickly release new products in the market with lower budgets?

Read More >>

More articles...
Adapting It's the Goal, Not the Role: The Value of Business Analysis in Scrum
by Ellen Gottesdiener and Mary Gorman


"Business analyst" is not a distinct role on Scrum or other agile teams. And yet, the goal for the team—to deliver high-valued product needs—requires strong business analysis skills. Ellen Gottesdiener and Mary Gorman describe the vital analysis work needed reach the goal, regardless of role.

.Read More >>
 
Mission Possible: ScrumMaster and Technical Contributor
by Steve Berczuk 

In an agile project, the ScrumMaster is a key role in the Scrum process and can demand a lot of work, especially when a team is transitioning to Scrum. This would suggest that the ScrumMaster should be a dedicated role for a team member. Teams trying out agile might not be able to justify a full-time ScrumMaster to the organization, so the role is filled by someone who is a contributor on the team. This can be a challenge and, if done incorrectly, a problem. This article discusses some potential issues to be aware of and how to make the hybrid role work.

Read More >>
 
 
 
 

 

Last Updated on Friday, 12 August 2011 12:21
 
Cialis

Agile Marketplace - Announcements and Special Offers

The Business Case for ALM Transformation
Are legacy systems holding your company back?  Breakthrough these technical constraints with an open and scalable environment that meets your unique business need to transform. There is no reason to be locked into an obsolete platform. The output of a number of recent transitions from legacy systems, this is practical white paper shares lessons learned and illustrates how guidance and enablement can pave the way for change.
Download this Whitepaper