agile
Articles
 |
Goal, Goal, Who's Got the Goal? Don Gray explains why software development teams need three common goals: long term, mid term, and short term. These goals focus a team and provide the glue that holds the team together. |
|
 |
Kanban and Lean Startup: Making the Most of Both Alexei Zheglov reflects on his startup experience and David Anderson’s kanban method in light of Eric Ries’ lean startup movement. Making the most of both approaches requires understanding how they relate to each other. |
Alexei Zheglov
March 29, 2012 |
 |
Dear Customer: The Truth about IT Projects In this personal and direct letter to customers, Allan Kelly pulls no punches and explains why IT projects don't always pan out for all of the parties involved. |
|
|
Management Myth #2: Only ‘The Expert’ Can Perform This Work How many times have you seen this in your projects: You need something specific done such as a new database, or a specific user interface designed, or you need a release engineer, or a user interface designer, or a part of the system tested and the normal person who does that work is not available? What happens on your project? Does it wait until The Expert is available? |
||
 |
Integrating Games to Change Behaviors, Part 2 Training people and introducing new ideas requires more than just clear, factual explanations or theorems. Brian Bozzuto explores how games, simulations, and other exercises play an instrumental role in helping people be comfortable enough with new ideas that they choose to put them into practice. |
|
|
Who Is Agile? {Book Review] Yves Hanoulle has edited a book, called Who Is Agile? I love this book because of all the back-stories, the pictures, and the links. And, oh my goodness, the links. |
||
|
Integrating Games to Change Behaviors, Part 1 Training people and introducing new ideas requires more than just clear, factual explanations or theorems. Brian Bozzuto explores how games, simulations, and other exercises play an instrumental role in helping people be comfortable enough with new ideas that they choose to put them into practice. |
||
|
Is Test Automation a “Project”? Test automation can turn into a real pain in the neck if a designated team is in charge of it or if the automators work on it as a separate project. In this article, Lisa Crispin seconds Bob Jones’s recent call for whole-team test automation and elaborates on the dangers of relegating test automation to an isolated project rather than integrating it into the overall software development process. |
||
|
Agile Lifecycles for Geographically Distributed Teams: A Case Study In this case study of a distributed agile team, the developers were in Cambridge, MA, the product owners were in San Francisco, the testers were in Bangalore, and the project manager was always flying somewhere, because the project manager was shared among several projects. The developers knew about timeboxed iterations, so they used timeboxes. Senior management had made the decision to fire all the local testers and buy cheaper tester time over the developers’ objections and move the testing to Bangalore. |
||
|
Why an Agile Project Manager Is Not a ScrumMaster A Scrum Master has only allegiance to the team. A project manager has responsibility to the team and to the organization. That means that the project manager might feel torn when the organization pressures the project manager to do something stupid. |
Pages
Recommended Web Seminars
Featured Resources
Visit Our Other Communities
AgileConnection is a TechWell community.
Through conferences, training, consulting, and online resources, TechWell helps you develop and deliver great software every day.