
Dive into the changes in the software industry that have gotten us to where we are today.
Change comes in many forms and at different frequencies.
Identify and categorize changes that occur during planning and execution, from detailed requirements to features or screen edits, and note their frequency and impact on the project.
Plans are a cheap and effective way to see the future.
What does it mean that no plan survives contact with the enemy?
Explore the difference between planning and execution by reflecting on real-life examples, examining granularity levels, and recognizing how changes during execution reshape professional planning.
No project gets anywhere without requirements, but gathering them can be challenging.
Explore interviewing techniques for gathering requirements by talking with stakeholders, echoing information, and achieving consensus on project scope, with insights drawn from media portrayals of suspects and witnesses.
Requirements are only part of the planning process; you have to estimate tasks to know where you're going.
What happens when you actually start to execute? The daily grind requires transparency and risk management.
Being able to lead a team is essential for career development, but it's a skill you need to learn.
Identify three qualities of good managers and illustrate them with real or aspirational examples, such as mentoring, standing up for the team with upper management, and helping career growth.
Master essential project delivery fundamentals with integrity, empathy, and concrete, actionable methods, bridging business and technical teams while advancing your career through mastery of requirements gathering, estimation, and management.
It's been a long road to get to where we are, smack in the middle of the ongoing "software crisis." Many software projects end in partial or complete failure, and the path to delivery is rife with challenges. This course is for you if you want to understand the different elements in play to delivering software and how they work together to provide a path to success. We'll start with how changes in the release cycle have affected delivery and move on to understand the fundamental nature of change and how different types of change affect delivery differently. We'll move on to covering planning and how to do it successfully within an environment of change. Planning is no good without execution, so we'll dig into the difference between the two and how one leads seamlessly into the other. Of course, you don't know what to plan if you don't understand what to build, so we'll talk about the challenges of requirements gathering and why it is so critical to get right. Bugs in your requirements are many times worse than bugs in your code. Another aspect of planning is estimation, which can be a fraught exercise. Estimation is both science and art, and there are many pressures to say what you think people want to hear rather than speaking the truth. Finally, we'll move on to the execution phase of the project and the importance of clarity and honesty in day to day work. Risk must be managed and people have to be wrangled. Speaking of wrangling people, we'll touch on day-to-day management of your team. Delivering software can be hard, but with the right soft skills, success is within reach.