- Initiating a Project
- Mobilizing a Working Group
- Drafting a Standard
- Balloting a Standard
- Approving a Standard
- Maintaining a Standard
- Software development approaches including agile
- DevOps throughout the entire software process
- Configuration Management (including the CMDB)
- Build and Release Engineering
- Source Code Management including branching and streams
- Deployment Engineering (DevOps)
- Continuous Testing
- Development in the Cloud
- Continuous Integration and Deployment
- Environment Management
- Change Management
The IEEE P2675 Standard for DevOps: Building Reliable and Secure Systems Including Application Build, Package and Deployment
IEEE P2675 – IEEE Standard for DevOps: Building Reliable and Secure Systems Including Application Build, Package and Deployment is now available for purchase from the IEEE.
This 95 page document specifies technical principles and practices to build, package and deploy systems and applications in a reliable and secure way. The standard focuses on establishing effective compliance and IT controls. It presents principles of DevOps including mission first, customer focus, left-shift, continuous everything, and systems thinking. It describes how stakeholders including developers and operations staff can collaborate and communicate effectively. Its process outcomes and activities are aligned with the process model specified in ISO/IEC/IEEE 12207, Systems and software engineering – Software life cycle processes, and in ISO/IEC/IEEE 15288, Systems and software engineering – System life cycle processes.
Call for participation in the IEEE P828 Standard for Configuration Management in Systems and Software Engineering
This standard establishes the minimum requirements for Configuration Management (CM) in Systems and Software Engineering, without restriction to any form, class, or type.
This standard describes CM processes to be established, how they are to be accomplished, who is responsible for doing specific activities, when they are to happen, and what specific resources are required. It addresses CM activities over a product’s life cycle. This standard is consistent with IEEE’s Software Engineering Body of Knowledge (SWEBOK), ISO/IEC/IEEE 12207 and ISO/IEC/IEEE 15288.
Need for the Project: We currently have only one active standard for CM (IEEE 828-2012) The current standard establishes the minimum requirements for Configuration Management (CM) in Systems and Software Engineering.
A revision of 828 needs to be consistent with the CM process as described in 15288 and 12207. The revised 828 should be consistent with the ISO/IEC 19770 IT Asset Management series and should answer the question of what CM data to track for what types of object. The revised 828 should recognize differences between hardware and software CM and could also discuss CM of services and should work with open source and current tools and release practices. The revised standard must be usable with any life cycle model and including Agile, Lean and iterative waterfall and the revised 828 must be aligned with IEEE P2675 – IEEE Standard for DevOps: Building Reliable and Secure Systems Including Application Build, Package and Deployment as well as related SC7 standards.
Ken Lynch is an enterprise software startup veteran, who has always been fascinated about what drives workers to work and how to make work more engaging. Ken founded Reciprocity to pursue just that. He has propelled Reciprocity’s success with this mission-based goal of engaging employees with the governance, risk, and compliance goals of their company in order to create more socially minded corporate citizens. Ken earned his BS in Computer Science and Electrical Engineering from MIT. Learn more at ReciprocityLabs.com .
- Need for training when adopting new technologies from Bitbucket to Ansible
- Automation of common tasks that everyone has become accustomed to doing manually
- Monitoring and addressing failed builds in the continuous integration server
- Improving coverage for automated testing from unit through functional/regression and don’t forget non-functional testing (including performance)
- Improving communication and collaboration by breaking down those silos (hint: get everyone to share a screen and show what they are working on)
- Bringing in a vendor every now and then and making sure their demo is focused on teaching best practices (instead of just a sales pitch)
- Making it cool to show off what your team is doing