|
Pivot, Pilot, and Adapt Anupam Kundu and Maneesh Subherwal explain how to operate in a global, hyper-competitive world while avoiding risk-laden experiments and other "stupid" strategies.
|
|
|
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.
|
|
|
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.
|
|
|
Agile Leadership for Mid-Managers Len Whitmore explores how the growth of agile changes the roles, responsibilities, and titles of mid-managers more so than any other management group, because agile practices require more leadership and less of what is considered traditional management techniques.
|
|
|
Specification by Example: Collaborating on a Scope without High-Level Control Understanding what the business users are trying to achieve can significantly help you focus the project on things that really matter. In this excerpt from Gojko Adzic's book Specification by Example, the author offers some tips for effectively collaborating on the project scope when you don’t have high-level control of the project.
|
|
|
From One Expert to Another: Simon Baker In this interview, author, speaker, and agile tester Lisa Crispin speaks with Simon Baker, cofounder of Energized Work and recipient of the Gordon Pask award, about the approaches and tools his lab uses.
|
|
|
Branching to Distraction Branching can be an effective solution for managing change, enabling parallel development and improved productivity. But, working on a branch is a distraction and can decrease agility, productivity, and code robustness. Learn when the value of working on a branch outweighs the cost.
|
|
|
Four Agile Tips to Eliminate Rework in Application Development Your applications need to meet business needs, overcome complex processes, and provide instant results to customers. And, ideally, they’ll require minimal rework on your part. The first step to success is requirements definition. Here, Filip Szymanski offers some tips from agile methods that will improve your requirements—even if you haven’t otherwise adopted agile.
|
|
|
Getting Empirical about Refactoring Often when we refactor, we look at local areas of code. If we take a wider view, using information from our version control systems, we can get a better sense of the effects of our refactoring efforts.
|
|