SUMMARY:

• key roles found at the front - end of a project, notably business analyst, product owner, functional architect, methodologist and at the back end, test planner and manager.
• Technical product manager and user acceptance testing lead-manager.
• Ttechnical documentation: notably business requirements, user stories, use cases, system specifications data models, object models and test scripting.
• Development skills allow Steve to relate well to developers.
• Has identified and developed potential revenue streams, cost optimizations and ways to reduce process cycle times, largest valued at over $8MM, next largest at approximately $1MM+.

SUBJECT MATTER EXPERTISE:

Software development, management of software development, broadcast advertising, staffing services, telecommunications, eCommerce, media, content management and cataloging, rights management, airline crew management, network provisioning, adult education, entitlement and provisioning (services), patent and patent claims construction.

SKILLS:

• Project management, system charter, business justification, scope and boundary definition, ROI analysis, project planning, facilitation (JAD and others), consensus building; strong sense of internal consistency
• Project management, favoring engineering/technical project management and agile methods.
• Requirements elicitation (functional and non-functional), business analysis, systems analysis, requirements specifications, business rules, system specification and design, functional design, object oriented analysis, object oriented design
• Strong Excel programming in VBA

TECHNICAL SKILLS:

Modeling: UML, use cases, use case diagrams, user stories, class diagrams, class models (domain, conceptual and logical), sequence diagrams, data models (ER diagrams) including conceptual, logical, dimensional and star schemata, business process (workflow) design and reengineering (including ‘swim lane’ variation), process hierarchies (process decomposition structures), state transition diagrams (including concurrent with dependencies), entity life cycle diagrams, event modeling (logical and physical), data flow diagrams, context diagrams

Architecture: business process architecture, functional architecture, services architecture, data architecture, object architecture, distributed systems architectures

Methodology: ‘Traditional’ software development life cycles (SDLC), Agile variations Scrum and Feature Driven Development

Testing: test planning, test cases, performance engineering

Software and technologies: Confidential Office (including Word, Excel, Visio, Access, Outlook and PowerPoint), HTML, SQL, SQL Server, SQL Server Management Studio, T-SQL, MS Access VBA, MS Word VBA, MS Excel VBA, C#, VB.net, Confidential Visual Studio, Confidential Team Foundation Server, Mercury/HPQC, Enterprise Architect (UML modeling), Rally, JIRA, SAP

ENGAGEMENTS:

Confidential

Product Owner; Engineering Project Manager

Responsibilities:

• Received CRs as user stories from the business and/or wrote them as requested by the business.
• Responsible for creating and managing our backlog (grooming, prioritizing and the like) for our application and interoperation with SAP
• Planned sprints and UATs around the numerous dependencies and competing factors including ‘out of cycle’ releases for pressing stories.
• Assisted the development team on technical specifications.
• Responsible for monthly UATs (Manila based testing team) and for writing the scripts.
• Developed a table-driven test case compiler that gave the testers rather detailed scripts by simply populating a set of tables. It is one of the reasons that we are able to keep up with the monthly stream of tax rate changes that are always occurring. Ask me about it.
• Acted as an aide-de-camp to a very busy Principal PM; our combined productivity was way more than the sum of each of ours’ would have been individually

Confidential

Business Analyst

Responsibilities:

• Assessing need with users (schedulers, trackers, pilots and flight attendants and their management)
• Discovering costs for the top ten most expensive process areas in crew tracking based on volume, degree of automation and error rate/rework
• Documenting as-is and deriving to-be workflows for two-dozen key processes
• Specifying system service integrations (ESB integrations) with other systems (inbound and outbound) using Tibco transport
• Deriving roughly 400 functional requirements in collaboration with the vendor and internal users team and managing them, including building auditable traceability to specifications, designs and test cases
• Conducting seminars (brown-bag and one-on-one) to selected staff on a suite of modeling topics (extracurricular activity)
• Designing a test-planning procedure for moving completed work into quality assurance; piloted and refined a testing protocol for base functionality and the services that the system provided and consumed.
• Test planning for delivered work packages.

Confidential

Architecture Analyst

Responsibilities:

• I was responsible for the radio requirements (management, prioritization, change control) interaction with business stakeholders about same.
• The development teams used Scrum.
• I developed user stories and associated success criteria, partnered with the product owner on features and priorities, participated in backlog grooming
• Occupied a number of roles including analyst, and architect for the “core”, the business object set that implemented the application’s core functionality and I was a developer in C# using Visual Studio and Team Foundation Server. Worked closely with subject matter experts.

Confidential

Technology Consultant; Business, Systems Analyst

Responsibilities:

• Designed functional architecture, business process models, data architecture for broadcast advertising certification.
• Designed the broadcast ad-placement to payment process (use cases and workflow) that includes advertisers, ad agencies, broadcast stations and financial institutions.
• Designed on-air content monitoring process (observation posts) and technique.
• Co-inventor of related Confidential IP; patents pending.
• Overall result: created a technically compelling basis for client’s funding proposals.

Confidential

Business Systems Analyst, Functional Architect, User Acceptance Test Designer, Test Lead

Responsibilities:

• As business systems analyst, gathered requirements from users (various techniques) wrote functional and non-functional requirements, use cases, functional specifications, business rules, wire-frame screen designs. As a Technical Lead for UAT in my area, tested and coordinated testing of others for Confidential, Credit and Collections functionality; responsible for defect logging, documentation and reproducibility analysis in Quality Center.
• As Quality Lead, mentor, troubleshooter, internal consistency agent for remainder of the team, I attended to the suitability, completeness and quality of the team’s collective work-product.