In Agile, items selected for development come from a backlog, a list of prioritized features describing functionality for the desired product. The inspiration for new features can strike at any time, but ideas may not be fully flushed out and can change as more is learned about the product. In this article, I’ve outlined 3 key elements of a healthy agile backlog that facilitate creativity, simplify ongoing development, and create a more valuable and profitable product over time.
Anything that gets measured and watched will improve. That’s why it’s valuable to leverage business intelligence tools that deliver insights throughout your organization. SQL Service Reporting Services, or SSRS, has been generating reports for countless companies for years. Recently, Microsoft has been putting more emphasis on its new Power BI service. With all the hype, you may be asking yourself if you should migrate that old SSRS service, or would it just be a waste of time and resources?
Lift and shift is a common cloud migration strategy that involves recreating the on-premise hosting infrastructure in the cloud while making minimal application changes. The benefit of this strategy is that it’s less invasive to the application code, and the hosting environment maintains a level of familiarity, which can be beneficial for teams working in the cloud for the first time. Once an application is stabilized in the cloud using the lift and shift strategy, the real fun can begin - taking advantage of cloud native features.
Though a consistent definition of DevOps can be hard to come by, one thing we can all agree on is that the goal is to improve software delivery performance. While the desired outcome is clear, the path to achieving it is a bit hazy. As a practitioner of EOS, the Entrepreneurial Operating System developed by Gino Wickman, Author of Traction, Get a Grip on Your Business, we’ve realized the value that a scorecard adds towards identifying and measuring the key actions that will make our vision reality.
In this article, we provide an overview of the scorecard tool and outline some ways it helps us deliver 99.99 software.
You’ve migrated your application to the cloud. Congratulations! Now that your code is in EC2 instances and your files are in S3, you’ll need to ensure everything’s secure. AWS uses a shared responsibility model in terms of security. This means AWS is responsible for security “of” the cloud, while you and your development team are responsible for security “in” the cloud. AWS will protect the infrastructure of the cloud, including hardware, software, and networking that run AWS services. Other security, including access to your AWS resources and the security of your application, is your responsibility.
Here is an overview of four of the most common AWS security features you’ll need to keep your cloud secure.