John J. Korak

11-Feb-2015

Beyond the Resume’…

Over the years I have been blessed to have had opportunities to work with outstanding people on interesting and challenging projects. The following pages are basically an expansion of the bullets points outlined on my resume. Included are snapshots of these projects, and images of the tools that were used to make things happen.

o Business Analyst Activities

o Agile Development Activities

o DoDAF Activity Modeling

o Process Documentation

o Process Training

o User Assistance Documentation

Thank you for taking the time to look.

John J. Korak

John J. Korak

11-Feb-2015

Senior Business Systems Analyst Over the last few years, I worked as a Business Analyst managing change requests to the Army Material Command (AMC), Logistic Support Agency (LOGSA) products and services.

This involved using the BABOK approach to requirements analysis to build dozens of requirement packages for LOGSA review and eventual software development. Doing this involved working closely with the principle stakeholders, the development teams, and the test teams.

The Jama Requirements Management tool was used to manage rqmt artifacts; however, I have also used simple Microsoft Office products (Word and Excel) and also the Sparx Enterprise Architecture tool. Other tools involved in this mix included: Atlassian Jira‎ Issue & Project Tracking SW, and Confluence

John J. Korak

11-Feb-2015

Agile Development

While working as a Business Analyst, on several occasions I operated as an Agile scrum master. The team worked through multiple sprints and I was responsible for managing the scrum, building user stories, and at the same time coordinating these with our UML-baseline, requirement artifacts.

I also had to capture and present status on activity burn-down rates and completions. And, of course, I had to manage the follow-on summary and prep for the next sprint.

John J. Korak

11-Feb-2015

DoDAF Activity Modeling

Recently, I had an opportunity to work with the Sparx Enterprise Architect application to build DoDAF activity models for process flow definition and analysis.

John J. Korak

11-Feb-2015

LOGSA’s System Engineering Process Documentation: Specifications

LOGSA implemented a new System Engineering Process referred to as the SEP. I was intimately involved in pulling together the suite of specifications that governed how LOGSA was to going to perform change management of their enterprise requirements.

The dozen related specifications were publish to the organization’s central library.

John J. Korak

11-Feb-2015

LOGSA’s System Engineering Process Documentation: Jama/Contour User Guide

I was responsible for creating a user guide to be used by LOGSA management for instruction on how to process requirement packages though the LOGSA approval board wickets.

At the same time, the document had to illustrate to contractor and government personnel how those same UML-based packages where to be built.

The result of this effort was a graphic-heavy, detailed user guide that illustrated, and walked through the process, with examples from the application.

John J. Korak

11-Feb-2015

LOGSA’s SEP Jama/Contour Training

After LOGSA implemented their new SEP and while working to build the user guide to be used by LOGSA, I began preparing for the next logical step in implementing a complete organizational change. That step was training.

I built a comprehensive package that demonstrated to LOGSA management how, using the Jama tool, new development was initiated by a request, and how a requirements package was promoted through the engineering process.

At the same time, the training demonstrated to contractor and government personnel how the Jama tool was used to captured UML-based, requirement artifacts for future use by development and test.

John J. Korak

11-Feb-2015

LOGSA’s LIW User Assistance

AMC LOGSA ‘s Logistics Integrated Warehouse (LIW) included a comprehensive user assistance package. At one point, I was part of a team responsible for maintaining over 13,000 pages of HTML-based assistance. We used a RoboHelp application to build not just a hierarchical help structure, but also pushed into a modern, context-sensitive, help structure. If the soldier could see it, we had to explain it.

Also, using a Captivate application, we created embedded visual tutorials into the help display.

John J. Korak

11-Feb-2015

LOGSA Commander’s Guide to LIW

I worked with LOGSA command to build a comprehensive, HTML-based service which outlined the organization’s products and services. The Guide was presented to the field through the LOGSA Website, and was also delivered as a CD-ROM.

The Guide included a multi-tiered, Frequently Asked Questions section which I had to derive from LOGSA helpdesk queries and from government functional interaction with troops in the field.

Below is the promotional brochure, which was featured at LOGSA conferences and included in LOGSA summary books.