Big Slick Design: 46 Questions for a Web Design Project. Agile Project Management and Life-Cycle Software. A Leaner Start: Reducing Team Setup Times. Face facts: Teams change I've worked with lots of teams in the past few years, some for very long periods, others for very short times. One common theme I've noticed with many of those teams is that the team composition always changes.
Usually, events beyond the control of any project trigger these changes: people fall sick or take holidays, project demands grow, new project opportunities arise or people simply want a change. Agile practices, like daily stand up meetings and pair programming, provide new members with all kinds of incidental information which may in fact be useless if they don't have enough context to hang it on.
Queuing theory applied to teams In manufacturing, lead time is traditionally split into four components, including: Setup - The time it takes to prepare the process before you can actually start running. Apply the same concepts to teams and the addition of a new team member and you get something that looks like the diagram below. About the author. David Seah: Better Living through New Media. NOTE The “Productivity Tools” menu supercedes this page.
Check it out The Printable CEO™ (PCEO) was born from a desire to focus my time more productively. For me, that means things that make my freelance practice sustainable and fun. The Printable CEO name comes from the idea that a good CEO should focus primarily on those things that move the company forward; since I can’t afford to hire my own CEO, being able to print one out seemed like the next best thing! In general, I use only one form at a time depending on what my needs are at the moment: High Level Goal Tracking for Freelancers and Small Business Owners - Download the Concrete Goals Tracker (CGT)Project-level Task Tracking - Download the Task Progress Tracker (TPT)Realistic Daily Planning - Download the Emergent Task Planner (ETP)Keeping Track of Planned versus Unplanned Stuff that Happens - Download the Emergent Task Timer (ETT)Keeping Track of Individual Task Assignments - Download the Task Order Up (TOU) The Task Order Up!
Conveying Agile Processes Concisely to Clients - Billy McCaffert. When beginning a new project of any appreciable size and scope, I always start with a project charter to define the project vision, the business case for the product, basic scope and critical success factors. I also use the project charter to clearly define, to the stakeholders of the project, the agile processes that will be employed to manage project development. If you've gotten to the project charter, you've surely already talked to your client about the wondrous benefits of agile development; the project charter is a great place to clarify these processes and get their buy-in.
Below is an example of the language I use to convey the agile processes and establish an agreement for management of requirements and communications. With this in place in the project charter, the client is made plainly aware of agile methodologies and enabled to set expectations, accordingly. Project Management Processes Process Releases Each release will be broken down into successive two-week iterations.