SUMMARY:

Fifteen years as an agile product owner or technical lead of local and geographically dispersed engineering teams. Over thirty years of experience successfully developing and delivering systems and management software. Extensive work in all phases of the software development lifecycle including design, development, support, and continued product engineering.

TECHNICAL SKILLS:

Programming Languages: JAVA, C, Assembly Language, Python, PERL

WORK EXPERIENCE:

Confidential

Product Owner

Responsibilities:

• I’m the Product Owner for two agile scrum teams developing Confidential ’s integrated IT management solution, OneView.
• The product has sold more than 1.3 million licenses helping drive the business unit to a billion dollar run rate.
• As Product Owner, I work with marketing, technical leadership, and the development teams to define and prioritize our backlog.
• I create and schedule the features and stories which describe the backlog and design its user - experience to seamlessly integrate into the existing product.
• Each sprint, as the teams complete their work, I validate it to ensure it fulfills the specified requirements and then demonstrate the completed stories to the stakeholders.
• Throughout the process, I continually groom the backlog and plan for future releases.
• In an organization of over fifty scrum teams, I am the only Product Owner responsible for multiple teams.
• I’ve succeeded by innovating.
• For instance, writing JAVA software which pulls d Confidential directly from Rally to provide enhanced dependency tracking Confidential what is available via the web user interface.
• I also led the teams in our transformation to the Scaled Agile Framework (SAFe) in which I am certified. In the more than fifty Sprints since we transitioned to SAFe, both teams have consistently met their schedule commitments delivering key features into the product.

Confidential

OnBoard Administrator Developer

Responsibilities:

• I was part of the team that developed the embedded software that runs Confidential Onboard Administrator for its blade system enclosures.
• Working in C, I worked on the software that managed enclosure fans and power supplies.

Confidential

Senior Engineer

Responsibilities:

• I worked a part of an agile scrum team that delivered new USB functionality into Confidential -UX.
• We successfully transitioned from an older product and developed new drivers which better integrated with Confidential -UX and drastically improved quality and performance.

Confidential

Technical Lead

Responsibilities:

• I led a team of five to ten geographically dispersed engineers responsible for fault isolation in Confidential -UX.
• The team members were Confidential -UX subsystem specialists who rotated assignment on the team. We concentrated on the version of Confidential -UX nearest release, requiring rapid turnaround on incoming defects in an intensely focused environment.
• This effort helped Confidential reduce the number of customer reported defects and shrink the “back end” of the development cycle in each subsequent Confidential -UX release.
• Working closely with engineers from various organizations, I provided thorough analysis of critical problems across a wide area of kernel subsystems.
• As lead, I focused on the most difficult issues, including system hangs, panics, and application failures.
• To aid in this work, I wrote defect analysis tools and trained other team members on the use of these tools.
• I trained and mentored new engineers in triage and debugging Confidential -UX.
• My consistent leadership helped the team remain effective and through ongoing management and staffing changes.
• To manage these changes, I worked across the many organizations within Confidential -UX to built support for the team.

Confidential

UX Development Engineer

Responsibilities:

• I was a member of the team responsible for the initial enhancements to support Confidential -UX on the Confidential Confidential architecture.
• I helped develop a model for high-speed networking based on d Confidential and process locality throughout the system.
• I worked closely with distributed development teams on support of a multinode networking implementation for this Confidential environment.
• I also worked on the design and development of a scheduler hint mechanism for Confidential -UX thread scheduling in a Confidential environment.
• This work included extensive kernel scheduler enhancements, the development of a new UNIX utility, and man page documentation of the new functionality.

Confidential

UX Networking Development Engineer

Responsibilities:

• I worked on the design and development of a high speed networking implementation on the Mach based micro kernel that Confidential used on its SPP platforms.
• This solution involved relocating much of the networking code from the microkernel to the per process emulator to ensure better d Confidential locality and performance.
• I was responsible for the design, development, and eventual support of a shared streams model to enable multiprocess access to networking connections.

Confidential

Internetworking Development Engineer

Responsibilities:

• I participated in the rearchitecture of our BSD sockets based TCP/IP networking code to a STREAMS based environment.
• I developed an in-kernel sockets to STREAMS conversion layer to allow the continued support of the socket-based interface to the rearchitected code.
• Eventually, I was the sole engineer supporting all kernel and utilities code for Confidential TCP/IP implementation.
• Where I drove the networking backlog to an all-time low.