Absolutely! Just a few differences in the public sector:
1. People, not customers - we're not (usually) selling anything
3. 100% + how goverment affects and could work with industry.
4. This. In the government context there's a lot of engagement!
Translating to gov...
1. How can we help people meet their needs? Is it a problem for gov?
3. 100% + is this problem solved, and can we buy it?
4. 100% + what is the mandate of the current government? How can we meet it?
@toddscanlan 3. Yes! Training for public servants in PM is crucial. The "but" is, we should absolutely be bringing in people from the private sector. They can work with experienced public servants to navigate the policies & laws.
Definitely! The biggest difference is that project teams typically measure themselves against completion and product teams chase after outcomes which will never be 100%.
Targeting and prioritizing outcomes over the output means the teams are given autonomy and equipped with the people to respond quickly.
1/2 It will be a tough change but a necessary one to serve people better. If we want people to have a better opinion of government digital services we need to build projects not to satisfy policies but people.
Yes! One of the best things about being a PM is learning from your colleages about their disciplines. Though, we're not (necessarily) going to be writing code.
Developers can absolutely become a PM, but the skill set is different - more organization, focus on users, and planning, than writing code.
1. Be as agile as possible. Have a tangible product so that everyone can look at it sooner. This isn't just for the benefit of learning from your users but also for internal organization to understand what we're shipping. This helps everyone evaluate risks much better.
2. Have a heart-to-heart conversation to understand what risks the requirements are trying to address to help you prioritize which ones are absolutely necessary, which ones you should have, and which ones are nice to have (MoSCow prioritization).
3. Work with the requirements team and bring them into the delivery team as early as possible. Agile teams mean everyone who is vital to delivery should be on the team...
How do we grow the community? By showing the value of what a PM does and making a strong case for multi-disciplinary teams. We have complex problems and need a variety of disciplines to tackle them.
A PM coordinates, sets the vision, and makes sure we're delivering value to service users.
Two barriers we'll need to tackle for the community to grow are in classifications / hiring, and separation between business and IT units in government.
Answer: Same premise as above, but always open to suggestions
Answer: This one is tough, still working on it
Answer: To start, have your developers sit with the business team.