information during the development process. User Story – Description of functionality a user wants, small enough to complete in a single sprint Epic – A large user story often defined for a release that spans of user stories or epics that may span multiple releases Teams often capture requirements in user stories and epics to provide a clear operational perspective of the capability’s purpose. User stories be completed. Epics are aggregations of user stories, often used to capture strategic intent. Epics may span multiple sprints and form a release, while user stories should be implemented within a single

time through incremental investments.  Managing the EA asset is an art, just as all strategic management is an art. Just as the CMO must sense market opportunities, weigh tactics for communicating with of buying off the shelf.  The risk of developing a system incrementally and altering it based on user feedback is often lower than that of buying a finished product that is hard to change.  The advantages product that does not fit our business and customize it until it does.  We offer our business users a user interface that is clunky because it was designed for users in the abstract across many possible companies

operations will derive NFRs. Codify these into the tests and pipeline f. BUILD REUSABLE OPERATIONS USER STORIES INTO DEVELOPMENT i. Goal – make recurring work as repeatable and deterministic as possible; testing efforts – Part 6: The Technical Practices of Integrating Information Security, Change Management, and Compliance 1. Introduction a. Goal to simultaneously achieve Information Security goals Pipeline a. INTEGRATE SECURITY AND COMPLIANCE INTO CHANGE APPROVAL PROCESSES i. Effective change management recognized different risks associated with different types of changes, to be handled differently

are being achieved. iii. Logging Levels 1. Debug – anything that happens in the program 2. Info – user driven actions or system specific 3. Warn – conditions that could become an error and will likely a termination iv. Examples of potentially significant events (Gartner’s GTP Security & Risk Management group) 1. Authentication/authorization decisions 2. System and data access 3. System and application INTEGRATING A/B TESTING INTO OUR FEATURE TESTING i. Random subset of users shown differing versions. User groups define a cohort. Statistical analysis of cohort’s outcomes from differing versions used to

through hands-on “shipping” of product. Management for the sake of management is not respected.  Get things done: The hierarchy must be flattened. Layers of management get in the way of goals. The employee employee wants the shortest possible path to shipping code without needing layers of approval. Management should be close enough to the action that they can demonstrate understanding—witnessing employees’ information, IT can lead the organization in learning and in deriving business value from good risk management and from making the most of opportunities that present themselves. Steward of Assets: senior IT

in Software Engineering Mike Ballou“There is no single development, in either technology or management technique, which by itself promises even one order-of- magnitude improvement within a decade abstract away its complexity often abstract away its essence • Not only technical problems but management problems as well comes from the complexity • It creates the tremendous learning and understanding I can help them I need…” • to Containerize the software, but to run that I need… • a Container Management Platform, but to network it I need… • a Service Mesh, but to secure it I need… • an automated Certificate

 working off a single backlog of features, driven by vision and roadmap  product and release management, release planning  program psi objectives  common sprint lengths - system continuous integration  business epics  architectural epics  kanban epic system – limit WIP  program portfolio management, enterprise architect  value streams  investment themes - provide operating budgets for release

dings Agile and EVMS They Can Co-exist! ( per John McGregor Deputy Director for Earned Value Management, PARCA, Office of the Assistant Secretary of Defense for Acquisition) https://www.acq.osd.mil/evm/ improving the defense acquisition process ... Agile in DHS: Bill Pratt, Director Strategic Technology Management, DHS OCTO. (linkedin.com/in/bill-pratt- 2431335)

Development  Operations (Operational Waterfall)  Infrastructure Ops  Product Ops  Product Management  Every technology under the sun  Solaris, Windows, Linux  Apache, IIS, TCServer, etc.  homogenization and assimilation – no snowflakes  Deployment methodologies, automation, monitoring, and management tested continuously. Steve Barr steve.barr@csgi.com @srbarr1 Overall Quality improvements, “it”

Security Stack enables: correlated and centralized logs, container security, east/west traffic management, a zero-trust model, a whitelist, Role-Based Access Control (RBAC), continuous monitoring, signature-based This can also be used to send notifications when there is anomalous behavior. 4. Vulnerability Management 5. A service mesh proxy to connect to the service mesh 6. Zero Trust down to the container