Jeffery Payne has led Coveros since its inception in 2008. Under his guidance, the company has become a recognized market leader in secure agile software development. Mr. Payne is a popular keynote and featured speaker at technology conferences and has testified before Congress on technology issues such as intellectual property rights and cyber-terrorism. Prior to Coveros, he was co-founder, CEO, and Chairman of the Board of Cigital, where he led the startup and growth of the company for 16 years. Mr. Payne is a former ACM National Lecturer and the co-founder of the Northern Virginia Chapter of the IEEE Computer Society. He holds a B.S. in Computer Science from Allegheny College and an M.S. in Computer Science from The College of William and Mary.
When an organization grows quickly, it puts stress on people, processes, and customers. Burnout happens, things fall through the cracks, and defects creep in. Unfortunately, many organizations try to scale agile too quickly, and that often leads to failure. Here are three of the telltale signs you’re scaling too fast.
The test pyramid is a valuable visual in agile. In particular, it argues that unit tests should make up the majority of tests, and while agile teams recite this principle, it is often not clear why it is so important. Here are five reasons unit tests should make up the majority of tests written for an application.
Continuous testing started when DevOps got hot as organizations began trying to figure out how to make everything in the software delivery process more continuous and testers felt they were being left out of the DevOps movement. If you want to get started with continuous testing, here are three things you should know.
There are lots of good practices that people will tell you aren’t agile. Usually this comes from people who read a book on Scrum or Extreme Programming and took it literally. But agile is not methods and tools associated with a particular methodology; as long as you follow the agile principles, anything is fair game.
With the trend toward a more continuous delivery and deployment process, late-lifecycle activities like security assurance present a significant hurdle to continuously delivering value to customers. DevSecOps addresses this by shifting security assurance activities, personnel, and automation closer to development.
If you are searching for agile knowledge, there are many books outside the current literature that may enlighten you. Some discuss the underpinnings of concepts we consider agile, while others are contemporary business books that present compelling ways to use agile effectively. Here are three Jeff Payne recommends.
Too often, organizations try to rush agile change. It is usually because they want to see the business benefits of agile as quickly as possible. Unfortunately, change doesn’t work like that—you can’t rush it. In fact, trying to change too fast often results in no change at all. Here are some examples to avoid.
The word continuous gets thrown around a lot when talking about agile and DevOps. One area that often doesn’t get enough attention is how to continuously build, test, and deliver secure applications.Just like for quality, you can’t test security in, so you need to have a plan for how to build it in from the ground up. Here are some tips on how to do that.
One of the principles behind the Agile Manifesto is “At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly.” Unfortunately, many associate that practice with performing team retrospectives at the end of a sprint, or periodically in kanban. But if you seek to build a high-performing team, there are more improvement activities you should consider adopting.
It seems like every other day, someone in the software development community feels the necessity to declare that agile is dead and they have something new and better. Sometimes it’s one of the founders of agile who now think the Agile Manifesto is dated and needs to be overhauled. Other times it’s ageless software veterans […]
