Shane Hastie and Johanna Rothman explain the challenges that come with distance, be it cultural, social, linguistic, temporal, or geographic. If you work to reinforce your collaboration habits every day, your geographically distributed agile team will thank you.
In order to be successful in the ring, a sumo wrestler needs to maintain a heavy body weight and at the same time be in peak physical condition. Just as these Japanese athletes have to find the right balance through a well thought-out combination of diet and training regimen, software development organizations need a balanced approach to implementing application architecture on agile projects.
Agile is recognized as a system-software development approach used to get quick feedback to keep the customer involved at every stage, building a disciplined team, and having working software at any given point in time. Sameer Arora writes on how things can fall out of place when agility on the programming side is ignored.
Richard Cheng explores whether or not federal governance controls are ready for agile implementations. If the federal government continues to implement agile without losing agile’s fundamental concepts, contractors and the government will grow in their understanding and ability to implement effective projects and deliver value iteratively and incrementally.
A written user story is a very short narrative—a sentence or two—describing some small piece of functionality that has business value. User stories are intended to foster collaboration and communication, but writing these short narratives poorly can negate agile’s flexibility. Charles Suscheck and Andrew Fuqua explain some common failure patterns that will help you focus on the right role, value, and business functionality when writing stories.
When it comes to agile development, Allan Kelly has noticed a lot of misinformation is being passed off as fact. In this article, Allan takes a closer look at twelve of the most common agile myths he has encountered while training new agile teams.
Being agile is difficult. Not only are there technical and organizational challenges, but the very nature of the way agile methods work brings the assumptions, context, and fears of team members to the foreground. These people issues are explored in Gil Broza’s book, The Human Side of Agile.
Kent McDonald introduces us to Arthur, a middle manager and product owner in a medium-sized insurance company who has been assigned to take on an agile project. For those unfamiliar with agile, the terminology and techniques of agile approaches can seem strange and often a little silly when not accompanied with an explanation as to why those techniques exist. Kent explains the challenges product owners like Arthur face and how to make product owners understand agile better.
Bob Martin and Bob Payne site down for a discussion about the importance of clean code on any project. Bob Martin is responsible for the CleanCoders.com video series, and in this podcast, the two Bobs get together to discuss the evolution of clean code's role in software development.
In this podcast, Bob Payne speaks with Jonathan Chashper about a variety of topics in the world of product management consulting. Jonathan brings a wealth of knowledge to companies of all sizes, in hopes of boosting revenues on any project.
Agile Test Automation
Successful Automation in an Agile Environment
Fundamentals of Agile Certification
A Pragmatic Approach to Adopting Agile
Be a Testing Rock Star
Agile Development Conference & Better Software Conference East
The Premier Collocated Conferences for Software Professionals
Recommended Web Seminars
Agile Connection is one of the growing communities of the TechWell network.
|Featuring fresh, insightful stories, TechWell.com is the place to go for what is happening in software development and delivery. Join the conversation now!|