Setting Product Development Priorities AgileGovCon 2017
•Descargar como PPTX, PDF•
0 recomendaciones•135 vistas
The document discusses setting product development priorities in government. It recommends prioritizing problems over solutions, using a framework that evaluates how solutions help users and agencies as well as whether they are future-focused and provide best value. The framework and a product roadmap example are presented, along with core principles of responsive, accessible, performant and secure development. Overall it promotes prioritizing initiatives based on a framework considering user and agency needs as well as long term strategy.
Recomendados
Recomendados
Más contenido relacionado
La actualidad más candente
La actualidad más candente (20)
Similar a Setting Product Development Priorities AgileGovCon 2017
Similar a Setting Product Development Priorities AgileGovCon 2017 (20)
Más de Kendra Skeene
Más de Kendra Skeene (6)
Último
Último (20)
Setting Product Development Priorities AgileGovCon 2017
- 1. Setting Product Development Priorities AgileGovCon 2017
- 2. Kendra Skeene @kskeene Director of Product GeorgiaGov Interactive
- 5. #AgileGovCon @kskeene Digital Product Strategy What Does That Look Like?
- 6. #AgileGovCon @kskeene Digital Products Have Limitations
- 7. You can’t always get what you want
- 8. You can’t always get what you want Audience gets what they need
- 9. #AgileGovCon @kskeene Problem First Not Solution First
- 10. Problem First What’s the problem? What do we hope to accomplish? What’s our current process? - Where are the gaps in that process? How will we know we’ve succeeded?
- 11. Roadmap Planning What is the problem? What is the severity? Who does it impact? Who can fix it? What is the estimated lift to fix it?
- 12. #AgileGovCon @kskeene Prioritization framework Does it help: Users Agencies Is it: Future Focused Best Value
- 13. #AgileGovCon @kskeene Does it help: Users Prioritization framework
- 14. #AgileGovCon @kskeene Does it help: Users Agencies Prioritization framework
- 15. #AgileGovCon @kskeene Does it help: Users Agencies Is it: Future Focused Prioritization framework
- 16. #AgileGovCon @kskeene Does it help: Users Agencies Is it: Future Focused Best Value Prioritization framework
- 17. #AgileGovCon @kskeene Does it help: Users Agencies Is it: Future Focused Best Value Prioritization framework
- 18. #AgileGovCon @kskeene Does it help: Users Agencies Is it: Future Focused Best Value Prioritization framework
- 19. #AgileGovCon @kskeene Does it help: Users Agencies Is it: Future Focused Best Value Prioritization framework
- 21. Product Roadmap 2011 2012 2013 2014 2015 2016 Platform Design Module Development Stable State & Bug Fixes Mobile Friendly Accessibility Performance 50 60 70 80 Numberofsites SSL Everywhere 2017
- 22. Initiatives impact long term strategy
- 23. Core Development Principles ✓ Responsive ✓ Accessible ✓ Performant ✓ Secure
- 24. #AgileGovCon @kskeene Core Development Principles Checklist http://bit.ly/devchecklist Takeaway
Notas del editor
- My name is Kendra, and I work for the state of Georgia in our digital services team. As Director of Product, I manage the roadmap for our enterprise Drupal 7 content management system. So I keep the pulse of the whole system - plan initiatives and enhancements, oversee maintenance, manage our training and support efforts, etc. More importantly, it means making sure the product we provide meets the needs of our agencies and their constituents.
- For context, that system supports the state of Georgia’s flagship site at georgia.gov, along with
- Close to 80 state agency websites across the executive branch, and some elected officials.
- To do that well, my team has to balance an always-growing wish list of features and tweaks from agency customers, while also keeping an eye on the changes in device use and industry best practices, so we can improve the platform for the needs of citizen stakeholders who often don’t have a real voice in the feature requests. This balancing act of prioritizing the roadmap for internal and external stakeholders is what product strategy is all about. So what does that look like?
- Digital product strategy is realizing that you can’t - nor should you - build every feature request that hits your backlog. This may sound obvious, but it means planning a way forward while keeping in mind how that will impact multiple stakeholder groups at multiple levels. How do you keep from drowning in feature requests and avoid the pit of reactionary development? You need a framework around how you prioritize your roadmap.
- To quote the great Mick Jagger and Keith Richards, you can’t always get what you want. Sometimes we have to say no to feature requests that would be a huge lift for minimal benefit.
- We trade off momentary whims and fancies in exchange for making sure the audience has what it needs to access key information / services
- It’s important for us to approach feature requests with a problem-first mindset, not solution first. We seek solutions to agency problems. We don’t jump right to asking “what module does this thing my customer asked for?” We ask “what’s the problem they want to solve with their proposed solution? What’s the best way to meet their goal?” Example - agency says “we need to see all your themes (or skins we can choose from for our design).” Or they’ll contact us and say “we need a new website design.” Now, the reflexive response is to jump right into a design conversation, or to send them a list of themes. But if we take a step back and start by asking them to state their problem, usually we find that they’re contacting us because they are overwhelmed by the amount of outdated content on their website - content that they manage. The solution is a content audit and content cleanup - not a new theme or new website.
- Let’s only jump into fixing things once we know what’s broken. If the toilet is leaking, we don’t need to start by repainting the bathroom. At that point it doesn’t matter that you hate the color of your walls. We need to turn off the water and get the ...uh… you know what… off the floor. For a lot of you, this will be a culture shift - a complete pivot in mindset. It’s not easy to break free from that instinct to just answer the question that was asked, or fix the thing someone asked you to fix, instead of asking questions and making sure you understand the problem first. So in response to a feature request, we need to follow up with probing questions. We need to ask (see slides)
- So once you have a handle on that problem, you can start to understand your options for addressing it, and chart out the priority for a solution. (review questions) … only then can we begin to 1) work out a solution, and 2) determine where this falls on our roadmap
- So once we understand the problem and we have a soltuion, we can move on to thinking through this prioritization framework. You can do this for any new feature requests, large enhancements, bug reports, and so on. (review slide) A couple of years ago, our team launched an Accessibility initiative to improve our platform code and themes to meet WCAG 2.0 (level AA) standards.
- From a prioritization perspective, here’s how that would look on our priority chart. First we ask, does it help our users? (explain)
- And you can see how that compares to another internal initiative for performance enhancements… (unpack).
- And then, compare that to a design and layout upgrade for the platform. (unpack) And this can be useful even as you think through he small requests. Remember that every change adds complexity, so even the seemingly small requests may have cascading results.
- The purpose of this exercise is to cut down on the complexity of the process, and distill it to some key goals. If this sounds useful to you, I’ve made this available as a PDF that you can download and print. I’ll tweet this link and share it on Slack at the end of my talk.
- Over the last six years, we’ve made a lot of small enhancements and improvements, along with the regular bug fixes and module upgrades to our product. But in tandem with those smaller updates and small releases, we’ve also prioritized broader initiatives with a bigger strategic impact based on the mindset that feeds that prioritization framework. These things - things like making sites mobile friendly, accessible to WCAG 2.0 standards, and improving page load speed and overall performance - didn’t come in the form of feature requests. Those are intrinsically driven because we’re watching the industry and responding proactively to the needs of that broader audience of citizens in search of government services.
- What’s key, then, is that as we complete initiatives, we build those principles into all future development.
- Our team has found value in prioritizing these development guidelines as our default expectations for anything new we build, based on the completed initiatives. This decision is based on an understanding of our audience, and our conviction that government is responsible for serving all citizens equally. Caps on a citizen’s mobile data plan, living in a rural area, or having a physical or mental disability should not be barriers to accessing government services online. These development principles get us to a baseline of providing the best effort for access to our services. Now, meeting these principles in our product development still requires intentionality at every stage - requirements, design, development, testing, and content management. They’re not part of a default mindset - if we don’t keep up on them as checkpoints in user stories and development sprints, and if we don’t test for them in each cycle, they’ll be forgotten.
- If those development principles match your goals, I’ve created a high-level checklist of things to look for to meet those development principles to get you started. It’s a google doc that you can copy and update as you see fit. I’ll tweet the link, as well, and share it on Slack.
- I could talk about this all day. And I and other team members have blogged about these and other related topics on our team’s website. So you may want to check that out as well. If there’s anything that struck a chord, let’s chat. Thank you. And with that, I’m off to our Q&A room. https://zoom.us/j/3422031143