As success with DevOps continues to make progress, it ventures into taking on other areas where traditional SDLC / IT practices have been less than optimal. Alongside this need, the IT Security technical landscape has been in rapid transition, making it near impossible for security teams to keep up with both increased DevOps velocity and the changing security landscape. Now, teaming up security in the continuous integration(CI) and continuous delivery(CD) model has a potential to be a game changer.
In the beginning, the movement started out being called DevOpsSec. ‘Sec’ was appended on to the end — almost like a caboose on a train – an afterthought. But in reality, security must be thought of, designed, and practiced throughout the process. In light of this, the more current term is DevSecOps – one where we weave security into our integration. Originally, marketing hype from each security software vendor clouded the concept. But, the movement is less about tools, and more about the way in which we work together, in parallel.
Dominion Consulting had the privilege of attending and sponsoring AgileDC last week. AgileDC is a great event every year. It brings the DC area’s best and brightest thought leaders and practitioners to talk about agile trends, best practices, experiences, and how to grow our practices and community. This event has much more of a community feel than many of the larger conferences and events, which I really appreciate and value. You can focus on forming new relationships and broadening your knowledge of local partners and clients, which benefits everyone.
When all of the best and brightest thinkers in the agile arena get together in one place, there’s no doubt you are going to learn a lot from one another and have fun. This year’s Agile2017 conference in Orlando was no exception. Great breadth of topics that loaded me up with ideas to bring back to our Dominion clients and our company itself. I want to share a few of the areas that top my list.
Making Time for Innovation is Good for Everyone
The innovation theme was prevalent in many conversations and areas, and there is a good reason – because it is important. Innovation is how people, products, industries, etc. get better. Allowing our developers, engineers and leaders the space to innovate will build higher performing teams and organizations. I spent Open Spaces time with some great agilists hearing about the innovative ideas they have implemented at their respective companies. This has fueled my fire to get this going even more at home.
Here at Dominion, we are currently building an internal application that will allow us to better track new business opportunities. Simultaneously, we are exposing more of our staff to agile and continuous integration/continuous deployment (CI/CD) principles. Among the many concepts we are trying to inculcate in our team is the “layer cake” user story.
The layer cake idea has been around for over a decade. However, I’ve found on nearly all agile engagements that I’ve been on, teams either discard this idea early in the project or completely ignore it from the outset. It is up to the triumvirate of the Product Owner, Scrum Master, and Business Analyst to ensure that the scrum team writes user stories in such a manner that the outcome of each story is working software that delivers tangible value to the end user. (more…)
You’re an experienced Scrum Master beginning a new project. You meet with your Product Owner (PO) for the first time and hear him or her say any or all of the following:
- “I’ve never worked in this role before.”
- “I’ll do my best to be on-site as much as possible.”
- “I’ve completed Certified Scrum Master training, but I’ve never applied it in practice.”
- “I’m the Product Owner for your team, and nine others.”
Your spidey sense is now tingling. You are going to be working with an inexperienced and/or overextended PO. Fear not, however. Here are some methods and remedies you can apply to get your PO up to speed.
Have you ever participated in a project where you felt there was no direction, no path forward? Have you asked yourself, How can we apply a process to our decision making? Here at Dominion Consulting , we had experienced this numerous times with clients and within our own internal projects. Our experience always led us to a solution but we wanted a better, more consistent, way forward.
Drawing from our efforts, we captured a series of best practices and lessons learned. Then, we created a model that would identify, assess, and road map a “problem solution.” We saw a need for a fixed period, firm fixed price assessment methodology that would provide our nonprofit customers cost certainty. After substantive development, we created a diagnostic framework that we have successfully applied internally and externally with our customers.
We introduce you to the Assembling, Assessing, Aligning, and Acting Diagnostic Framework. Or more simply, A4. (more…)
A few years ago, I started introducing Definition of Ready to help alleviate a common challenge I was seeing. User stories were coming into the sprint with little information and weren’t making it to Done. The team spent more time talking to the Product Owner about what they wanted than developing it.
As an agile enthusiast, I was aware of the latest updates to Scrum guidelines and introduced Definition of Ready thinking this will solve our problem! I met with the team, setup a few guidelines as reminders of what should be in a story, we were set! Over time, through retrospectives, these guidelines morphed into something I started to realize no longer made us an agile team.
Last month, I attended the 2016 Amazon Web Services re:Invent conference with Jed Carr, Dominion Consulting’s Director of IT. I went primarily with a DevOps focus, trying to expand our continuous integration and continuous delivery (CI/CD) capabilities by picking up some best practices by a leader in the market.
While I did attend some excellent break-out sessions, the specifics of each could bear it’s own blog post, there was a singular idea that came up during every session, keynote, or chat around the coffee pot.
Software moves faster than ever.
Successful software delivery is no longer measured in years, quarters, or months. We measure it in weeks, days, and hours. According to Puppet and their 2016 State of DevOps Report, high-performing IT organizations deployed 200 times more frequently than their low performing counterparts. So if you’re an organization pushing out quarterly releases, you’re trying to keep pace with the front-runners pushing out twice daily.
It is hard to believe that Dominion Consulting is approaching its 14th year as an organization. It all started for some of us in 2003, when two Enterprise Resource Planning experts decided to build a company based on SAP, and its rapid growth in the Federal Government. Fast forward to 2013, a core capability was our SAP expertise and rapid growth into the Momentum Financials arena. Now, as 2017 begins, our Enterprise Applications solution area is at a crossroads. We are excited about the new direction it is taking us.
This year marked the 15-year anniversary of the writing of the Manifesto for Agile Software Development. Today, I can’t help but marvel at the impact this collection of simple, yet elegantly stated principles continue to have, especially here in Washington, D.C.. Agile has not only changed how we build working software, it has fundamentally changed how we understand our organizations and how we define the business value we produce. With agile, many of us have learned new approaches to prioritizing our work at an enterprise scale, how we can organize our businesses, and even how we can build deeper relationships in the process. Agile development has sparked a new wave of innovation, especially in the Federal market and it’s incredible to think what 2017 will bring.
For those who are doing it successfully, being agile requires the adoption of both an agile-mindset and the incorporation of new software architectures and delivery practices. At Dominion Consulting, we recognize that our clients have very specific needs and objectives for their implementation of agile solutions. We work closely with each client to provide their desired results. Agile is, of course, not without its challenges. Whether it is initial adoption, sustaining agility at scale, or breaking into a more effective CI/CD model, these challenges are significant. I’d like to share a few key observations and strategies that have helped our clients hit their stride with agile.
Subscribe to Dominion's Blog via Email
- Blazing a Bright Path to the Future as TeraThink
- As if DevOps was Not Enough…DevSecOps
- Building the Local Agile Community at AgileDC 2017
- Looking at the Future of Digital at SAP TechEd 2017
- Congratulations Laurence Hart, The Information Coalition’s 1st Honors Fellow
- Dominion Walks to End Alzheimer’s
- People First These Days in Information Governance
- Fall is Coming So It Must Be Time for Dominion’s 2017 Veteran’s Day 5K Race