We have 5249 guests and 8 members online
Featured Whitepapers
- Apples, Oranges, and Acorns - All Agile Development Tools Are Not the Same
- One's Enough for Agile Application Development Management
- Requirements Management 101 – 4 Basics Everyone Should Know
- Tips on Requirements Traceability – Learn How to Control Change and Improve Quality
- Scaling Continuous Integration to Large and Distributed Teams
|
Agile News - September 2008
 We have quite a variety of articles for you in this month’s issue of the Agile Journal. They vary from getting back to basics, to examining common success and mistakes of Agile adoption efforts in progress, to articles that cover new ground as Agile is taken into different environments. A significant portion of this month’s articles come from authors whose experience is primarily in large organizations adopting Agile development practices; you will find many unexpected and insightful suggestions which are not yet in the mainstream.Jochen Krebs warns us about teams trying to move too fast as they adopt Agile development practices shows us how to spot the early signs of burn-out in Finding the Steady State. Daryl Kulak and Anita Shankar share their experiences in hiring for Agile team members within a large organization that has a non-Agile culture and give us Agile Interview Questions as a guide to hiring managers. Building a product for what a customer needs is one of the core tenets and promised benefits of Agile development. In this month’s issue, we have two articles that touch on this issue: Cesario Ramos and Eelco Gravendeel continue with their advice in part 2 of The 9 pitfalls of Scrum one of which is the “defective product owner” while Tim Snyder examines the responsibilities of the product owner role in It’s a Tough Job… but Somebody Has to Be the Product Owner. Sean Sheehan compares software projects to taking a road-trip with his family in Writing Shippable Code, the first article of a three-part series, and compares Agile software development to having a global positioning system (GPS) in your car. He sets the stage for the next installment, which will examine loopholes in current Agile software development practices that allow a team to bypass the customer. In the case study for this issue, Agile Using Offshore Development: The Costs and Risks, Kevin Coleman shares the costs, risks, and rewards of an Agile team working in the U.S. working with a waterfall team offshore. In his monthly book review, Brad Appleton takes a look at Alan Kelly’s Changing Software Development – Learning to Become Agile. Finally, in From The Editor, I give you a preview of our plans for change over the next few months as we move towards a new format and cover new areas of our evolving Agile community. Amr Elssamadisy
|
|||||||||||||||||||||||||||||||||||||||||||||||||
| Last Updated on Wednesday, 08 September 2010 10:14 |
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