Upcoming and Recent WebCasts
- Performance and Reliability Trade-Offs for Tuning ActiveMQ
- Best of Both Worlds: Enterprise ALM and Agile Parallel Development Practices
- Making the economic case for build-test-deploy automation and acceleration
- Enterprise Continuous Integration Maturity Model
- Subversion Best Practices: Maximizing Productivity
Agile Poll
Send us Feedback
Click here to send us feedback Agile Journal
Agile News - Sep 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
Editor-in-Chief
Agile Journal
Agile Journal is an online magazine and e-newsletter focused on providing readers with the need-to-know information and resources they need to develop software for an agile business. For over three years Agile Journal has delivered thought leadership and pragmatic advice from a wide range of industry experts, as well as direct feedback from hands-on developers and project managers.
Review Previous Editions | Subscribe | Contact the Editors -- Read the Current Edition Below
Agile News - Sep 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
Editor-in-Chief
Agile Journal
| Featured articles... |
|
|
|
| More articles... |
| ||||
| ||||
| ||||
| ||||
| ||||
Agile Marketplace - Announcements and Special Offers
Complimentary Webinar w Forrester Analysts on Agile and Lean ALM
Complimentary webinar with Forrester Analysts Jeffrey Hammond and Dave West. Learn about Lean ALM Development, optimizing processes, cutting costs and compliance by design.
Read More
Agile CMMI – The Best of Both Worlds
Shares how a leading financial institution gains CMMI level 3 compliance and supports Agile practices.
Register for CollabNet webinar May 21
Requirements-based testing (RBT) can help you increase efficiency, reduce project risk, and improve overall software quality. Learn how MKS Integrity for application lifecycle management enables RBT, delivering full lifecycle traceability to help ensure that project requirements have complete test planning and execution coverage. Download the Requirements-Based Testing whitepaper