agile Commitment Driven Planning Commitment Driven Planning (sometimes called Capacity Driven Planning) is a technique that lets a team determine how much work to bring into the sprint based on how much time they have to do said work.
agile Retrospective: Setting Expectations Setup For this retrospective you’ll need sharpies, post-it notes and a wall, window or whiteboard on which they can be stuck. Setting Expectations At the heart of this retrospective exercise is defining
agile Building a Self-Sustaining Ecosystem through Agile Coaching I was recently fortunate enough to attend the Culture Conference in both Philadelphia and Boston. Even more so, I was able to enjoy the company, conversation and new relationships as a member of
agile Agile Principles: Progress Requires Working Software Working software is the primary measure of progress. – Principles behind the Agile Manifesto Pixel perfect design mockups, UML diagrams, detailed user stories, automated tests, thousands of lines of code and hours of discussions.
agile Add Fun to Your Scrum Board Physical Boards Please I recently started working with a team who had been introduced to scrum as part of their organization’s adoption of agile. Their only experience with scrum was through the
agile Retrospectives: Best Practices, Common Problems and New Ideas Here are the slides for my presentation at the May 2012 Phoenix Scrum User’s Group meeting. If you attended the meeting and have any further questions, please contact me. Retrospectives: Best Practices,
agile Agile Principles: Tear Down These Cubes The most efficient and effective method of conveying information to and within a development team is face-to-face conversation. – Agile Principles Manager, Tear Down These Walls If you were tasked with designing a system
agile Agile Principles: Self-Organizing Teams are Motivated Teams Build projects around motivated individuals. Give them the environment and support they need, and trust them to get the job done. – Agile Principles Self-Organizing Allow the people doing the work to self-organize and
agile Agile Principles: Collaborate Everyday Business people and developers must work together daily throughout the project. – Agile Principles Email is not Enough Working together involves more than exchanging e-mails about the software. It’s more than passive instant
agile Agile Principles: Frequently Deliver Working Software Deliver working software frequently, from a couple of weeks to a couple of months, with a preference to the shorter timescale. – Agile Principles Quick Feedback A short feedback cycle is incredibly valuable.
agile Probability, Velocity and Re-Estimating User Stories When working with user stories, story points and SCRUM, it is not uncommon to come to the end of a sprint and realize that a smaller story took longer to complete than a
agile Agile Principles: Iterate. Evaluate. Repeat Welcome changing requirements, even late in development. Agile processes harness change for the customer’s competitive advantage. The first thought here is the means, the second the end. Let’s start with the
agile Let Conversations Write Your Tests This shift in thinking is due in part to Liz Keogh’s Step Away from the Tools and Dan North’s Who’s domain is it anyway?. Both of these got me thinking
agile Agile Principles: Deliver Early and Often, but Always Deliver Value The Agile Manifesto describes twelve principles of agile software. In a series of twelve blog posts, I will explore each principle. Our highest priority is to satisfy the customer through early and continuous
agile Do You Make This Common Mistake When Estimating? When estimating a project using the Planning Poker method, many developers like to use a baseline estimate for a given task. For example, many developers use CRUD, the creating, displaying, editing and deleting