People & Teams
Articles
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. |
||
Management Myth #1: The Myth of 100% Utilization Too many managers believe in the myth of 100% utilization—the belief that every single technical person must be fully utilized every single minute of every single day. The problem with this myth is that there is no time for innovation, no time for serendipitous thinking, no time for exploration, and it often leads to a less successful organization. |
||
Empowering Agile Teams Teams, when truly empowered, will always make better decisions than any one individual. Where can you empower teams as you adopt agile? |
||
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. |
Len Whitmore
December 28, 2011 |
|
![]() |
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. |
|
Leadership, Management, Transitioning to Agile Johanna Rothman has worked with several management teams who want her to train them or their project managers to take over the agile training. While on the surface this doesn't seem an unreasonable request, when one considers the self-managing, self-organizing nature of an agile team, the incongruity of this thinking begins to shine through. |
||
![]() |
Behavior Unbecoming of a Leader One of the most important roles of a leader is to serve as a role model for others in the organization. In this article, Naomi Karten describes a situation in which a CIO forgot this responsibility, almost taking action that would have undermined his efforts to reverse the IT organization’s plunging morale. |
|
Updated Agile Program Management Slides Posted I missed one presentation in my last post. At Oredev, I had an opportunity to speak with the PMI Sweden folks (at least, the southern Sweden folks). I talked about Agile Program Management, and discussed my current thinking about agile program management. |
||
Who Defines “Success” for Your Project? An otherwise good project management book provokes Payson with definition of “success” that rubs him the wrong way. In this article, he presents his case. |
Pages
Recommended Web Seminars
On Demand | Building Confidence in Your Automation |
On Demand | Leveraging Open Source Tools for DevSecOps |
On Demand | Five Reasons Why Agile Isn't Working |
On Demand | Building a Stellar Team |
On Demand | Agile Transformation Best Practices |