Job Seekers, Please send resumes to resumes@hireitpeople.com
Overview:
We believe there is an opportunity to optimize the user experience by looking at the automation strategy more holistically, potentially harmonizing how the tools are accessed, or consolidating the user experience. This effort should analyze the scope of the opportunity from the perspective of three primary personas, and articulate how the current tool-set is being utilized, and how it could be improved.
SCOPE/DELIVERABLES of this ROLE:
**Document three key personas (Software Engineer, Product Owner, Scrum Master) as well as the primary use cases that dictate their tooling needs.
**Document current tool-sets utilized by each persona mapping back to use cases.
**Formalize series of recommendations focused on improving usability and adoption.
Today there is a large set of tools used in the software development processes. Below is a subset of the tools known to be commonly used by project teams.
Chef
Cloud Formations (infrastructure provisioning on AWS).
Udeploy
GitHub
Subversion (source code management).
vCAC (infrastructure provisioning on private cloud).
Hudson
Access Central (access provisioning).
HPSM (change tickets, exceptions).
Archer (waivers)
Version One (agile story management).
Home-grown portals (laptop provisioning portal, Java self-service portal, OMS)
Wiki sites (via Pulse).
This financial institution has changed our technology and labor strategy to in-source more work, and to leverage more native written software applications. This is driving a large demand towards different tools that are used to manage different aspects of the software development lifecycle. While each individual tool serves a valid purpose, there is a general proliferation of tools which may create confusion across the various stakeholders and potentially not gaining the overall value of the technology. This effort will create a strategy that first documents the domain, then proposes solutions that will make work more efficient across the enterprise.
