Good day TC!
I’m acting on Mike Winkler’s request to produce and maintain a list of prioritized skill set needs – this can be helpful when recruiting new participating institutions. This list would be owned/maintained by the Technical
Council. So, here is what I put together for dev/devops checklist. And I chatted with Harry to put together the PO list.
Wondering if we
-
Can agree on the skill set
-
Publish it off the wiki or elsewhere
Thoughts/comments? I don’t know if we’ll have time to cover it in Wednesday’s meeting or whether we can discuss via email or slack.
Developer skill set:
(this is a list for a back-end developer; for a front-end developer, #5 would have to be swapped with #1)
-
Java 8 & Object-Oriented Design/Programming
-
Implementation of RESTful interfaces in a microservices model (RAML, JSON, XML)
-
Databases, both SQL and NoSQL – PostgreSQL specifically is a plus
-
Virtualization – Docker, Vagrant
-
Client-side Javascript (React) and related tools/frameworks
-
Test tools/frameworks
-
CI/CD – Jenkins
-
Server-side Javascript (Node JS) and related tools/frameworks
-
Security – SSO, OAUTH, SAML, LDAP, etc.
-
SCM - Git/GitHub
DevOps skill set:
-
SCM (Git/GitHub)
-
CI/CD – Jenkins
-
Virtualization – Docker, Vagrant
-
Infrastructure Automation – Ansible, Puppet, Chef
-
Orchestration – Kubernetes/ECS, Rancher
-
Security -- – SSO, OAUTH, SAML, LDAP
-
Cloud - AWS, GoogleCloud
PO Primary Responsibilities
-
Own the team backlog, contribute to program vision and roadmap, Key stakeholder in story definition assisting the team with clarification, estimates, story sequencing and team objectives for each sprint
-
Backlog refinement – Build, prune, and maintain the team requirements backlog (consisting of features, user stories, defects, and enablers) with input from the SIGs as key stakeholders
-
Iteration Planning – Review and prioritize the backlog for iteration planning, including coordination of dependencies with other product owners
-
Be the main source for feature detail and priorities for the development teams
-
Responsibility for accepting the final iteration plan on behalf of the development team
-
Just in time story elaboration – Keep the process flowing (balance between stale stories and inhibited flow of new stories)
-
Drafting story acceptance criteria and providing examples when feasible
-
Accepting stories into baseline
-
Validate that the stories meet acceptance criteria and completeness; meets Definition of Done
-
Validates fitness for use
-
The team member empowered to accepts stories (i.e. requirements) as truly done
-
Participating in team demo and retrospective
-
As a key member of the team and the one person responsible for requirements, key in driving and developing the team demo
-
As a key member in the team retrospective helping drive improvements across the team and project
-
Coordination of dependencies with other product owners throughout the sprint
-
Manage communications and relationships with diverse stakeholders, ranging from Product Managers, Project Managers, developers, designers, QA engineers, architects and the key SIGs
--
Mark Veksler
Director, FOLIO Development - EBSCO Information Services