|
Save Your Sanity: Planning During a Health Care Crisis A health care crisis can hit without warning, leaving you both nursing the patient and mired in seemingly endless bureaucracy. In this article, Kathy Iberle shares with us her experience dealing with an elderly uncle who suffered a stroke and how agile methods, like using a visual planning board, can help one prepare and be ready when disaster strikes.
|
|
|
Top Twelve Myths of Agile Development 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.
|
|
|
Visualizing All the Work in Your Project Portfolio Regarding project portfolios, it can be a big problem for clients to see all the work. Some clients have multiple kinds of projects, so they want to show their work in a variety of ways. Johanna Rothman describes some helpful ways to display the work being done.
|
|
|
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.
|
|
|
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.
|
|
|
Agile Lifecycles for Geographically Distributed Teams: Using a Project Manager with Kanban, Silo'd Teams This is a product development organization with developers in Italy, testers in India, more developers in New York, product owners and project managers in California.
This organization first tried iterations, but the team could never get to done. The problem was that the stories were too large. Normally I suggest smaller iterations, but one of the developers suggested they move to kanban.
|
|
|
A Productivity Comparison of Kanban and Scrum Charles Suscheck compares the levels of productivity of Scrum and Kanban through a hands-on experiment that he and his team personally participated in. Learn the upsides and warnings about each practice to help you decide what might work best for you and your team on your next project.
|
|
|
Kanban System Design Karl Scotland explains that viewing kanban as a systemic approach leads to systems thinking. Systems can be thought of as being made up of elements, which interact to meet a purpose. They are more than the sum of the parts, and the system’s purpose is crucial in determining the system’s behavior.
|
|
|
An Overview of Lean-Agile Methods Life used to be simpler. In the early 2000s, if you wanted to go "agile," XP was the route of choice. And then Scrum became popular. And it was not too long before organizations began to hit the limits of these approaches due to their focus on teams. And then it became apparent that lean principles could be applied to software and Lean Software Development and later Kanban were added to the mix. Now, you have a great many choices: Not just about which method to use, but where to start, whether to go top-down or bottom-up, and what should be the scope of your effort.
|
|