Kent J. McDonald is an author, speaker, and coach. His more than fifteen years of experience includes work in business analysis, strategic planning, project management, and product development in a variety of industries including financial services, health insurance, human services, nonprofit, and automotive. He is coauthor of Stand Back and Deliver: Accelerating Business Agility.
In agile, there are different types of planning at various intervals and levels of detail. One of those levels is release planning, which is the intermediary type of planning between deciding what is included in a product and what the delivery team will focus on for the next iteration.
Kent McDonald explores the idea that using an agile methodology is akin to improvisational theater. Like every metaphor for agile, improv theater does fail in some points, but it can be helpful when viewed from the perspective of collaboration.
Due to the popularity of Scrum, the idea of having a product owner has taken hold of development professionals and is used by teams that are not even using Scrum. With this industry-wide adoption, the definition of product ownership and the product owner's role has evolved.
An interesting paradox many project teams face is that while collaboration is highly valued, collaboration often takes the form of one of the biggest time wasters humans have ever invented—meetings. Kent McDonald explores effective approaches to leading an effective meeting.
The jobs-to-be-done (JTBD) theory is intended to help stakeholders think about their products and services by considering how their customers like to use them. Kent McDonald delves into the JTBD theory and its benefits to a product delivery team.
One of the more often repeated phrases from the lean startup and customer development lexicon is the admonition to "get out of the building" in order to meet and learn about customers. What project teams should take away from this idea is the need to interact with stakeholders to address problems.
Software development teams that want to automate their regression testing suites may wonder if there is any way to see the forest for the trees regarding their numerous story tests. Kent McDonald explains how to perform effective automated acceptance testing amidst all the noise.