This talk may contain strong language, harsh truths, and serious passion.
Project management is the use of specific knowledge, skills, tools and techniques to hamper developer productivity.
Project management is the use of specific knowledge, skills, tools and techniques to deliver something of value to people.
Too much time in meetings
Requirements changing on the fly
QA reporting back bugs that aren't bugs
Sprints resulting in missed deadlines and deathmarches
Bugs missed in planning that resulting in overtime work
Too little or too much process
Micromanaging
Burn down chart driven development
Unable to determine project timelines
Stand-ups so long your chair thinks you ghosted it every morning
In order to win the game, you have to know the rules.
Waterfall project management is a linear approach to delivering a project where phases are distinct & must be completed sequentially.
Agile project management is an iterative approach to delivering a project throughout its life cycle.
We are uncovering better ways of developing software by doing it and helping others do it.
Through this work we have come to value:
Individuals & interactions over processes and tools
Working software over comprehensive documentation
Customer collaboration over contract negotiation
Responding to change over following a plan
That is, while there is value in the items on the right, we value the items on the left more.
They share Agile philosophy, roles, and sometimes ceremonies.
https://badsoftwareadvice.substack.com/p/how-to-avoid-understanding-the-business
Kanban is a framework that provides visibility to an entire process and is commonly used for agile and DevOps to drive continuous delivery and improvement.
Extreme Programming (XP) is an agile software development framework that aims to produce higher quality software, and higher quality of life for the development team.
Agile is a mindset, SCRUM is a framework. SCRUM describes a set of meetings, tools, and roles that work in concert to help teams structure and manage their work.
The Scaled Agile Framework® (SAFe®) is a system for implementing Agile, Lean, and DevOps practices at scale.
"None of the Above" and "all of the above" are also options 😬
Project management should help software development productivity and provide visibility, not hamper and obscure it.
When they're used effectively they can improve productivity
"Could we table this discussion, and set another meeting to go more in depth with the people who need to be there?"
Capture key points of technical decision making discussions and save in your company wiki.
Ensure your calendar is up to date, and politely but firmly maintain boundaries around it.
Set up blockers for focus time, or propose a weekly "office hours" for question-asking regarding tech.
What's going well?
What Should We Continue Doing?
What Should We Stop Doing?
"I think if we had a retrospective to review our process and talk about things that went well and discuss things we could do better, it would improve our ability to meet X,Y, Z goals. I'll schedule a recurring meeting for us!"
"Process does not exist unless it is documented" - Jennifer’s first rule of Project Management.
Process should aid development & help people follow the same steps to handle issues. Process includes tools like internal wikis, issue trackers, version control, UX feedback, QA feedback, deployment and more. Process should be iterated on and improved to avoid repeated bottlenecks
"Ready" means that stories are be immediately actionable. The Team must be able to determine what needs to be done and the amount of work required to complete the ticket for it to be considered ready.
Me when I'm not constantly begging for information about my assigned tickets every sprint because our team added 'requirements complete' to our definition of ready.
"Done" is an agreed-upon set of items that must be completed before a project or user story can be considered complete. It is applied consistently and serves as an official gate separating things from being “in progress” to “done.”
A workflow can be defined as “orchestrated and repeatable pattern of activity”. Workflows must be created to execute on work. To create an appropriate workflow you may need to answer questions like:
How does the work that needs be done get described to the developer?
Are there mockups representing the work?
How are mockups delivered and described?
How can the developer verify the work has been completed?
How should a QA be able to test work?
How can acceptance criteria be created?
How should deployment work?
Is there user testing?
What happens if an issue is blocked?
Does code need to be reviewed in PRs?
Any individual, group or organization that can affect, be affected by, or perceive itself to be affected by, an initiative
Timeline? Reopened tickets? Deployment times? Number of showstoppers?
Who do they answer to? What are their concerns? What are their pressures?
The more you understand about your PMs motivations, the better you can help guide them towards better practices (and away from micro-managing)
A Gantt chart provides you the timeline view of your projects. It allows you to visualize how different tasks/activities of a project are connected with each other and how they fit in the overall timeline of the project.
A burndown chart shows the amount of work that has been completed in an epic or sprint, and the total work remaining. Burndown charts are used to predict your team's likelihood of completing their work in the time available. They're also great for keeping the team aware of any scope creep that occurs.
Slides available at:
https://tehfedaykin.github.io/DevelopersGuideToProjectManagement
Need help with Project Management and supporting more effective development teams? Work with me! jennifer@bitovi.com