Related Content
 |
Don’t Ask for Permission or Forgiveness—Use an Agile Alternative Some teams get around bottlenecks by taking a “better to ask forgiveness than permission” approach. This may be expedient, but it doesn’t provide a path to changing the organizational dynamic, and it can lead to wrong decisions when wider input is advisable. A more agile way is to take an “I intend to” approach. |
|
 |
If Santa Can Be Agile, So Can You To improve his toy development lifecycle, Santa Claus had the North Pole move to an agile and DevOps approach. Santa knows it's important to accept requirements late in the process, work incrementally, deploy on time, and—above all—focus on the customer. Here’s what he found to be more effective with agile and DevOps. |
|
 |
Security Testing: A Constructive Mindset with a Destructive Approach A typical tester mimics end-users, who are constructive when exploring an application’s functionality. But the role of a security tester is different. Their focus is mainly on mimicking hackers, who are intentionally destructive. A solid security strategy should balance both constructive and destructive efforts. |
|
 |
2 Ways to Know Your Work Is Actually Done Some people think a good indication that a piece of work is done is if it's been tested. But by whom, and how? Testing alone doesn’t specifically determine whether you are done—especially when we probably don’t mean the same thing when we all talk about testing. Here are two ways to know when your work is truly done. |
|
 |
4 Tips to Refocus Stale Standups The daily standup is supposed to get everyone on the same page and make teams more productive and efficient. But it’s easy for this short meeting to become stale and stop providing any real benefit. Here are four ways to get out of the slump of merely delivering status updates and re-energize your daily standups. |
|
 |
Is Your Culture about Responsibility or Blame? When things go wrong, it can be helpful to understand what happened and who was involved. However, all too often organizations (and the managers within) confuse responsibility with assigning blame. The former is essential for improvement. The latter works against an effective, collaborative, productive culture. |
|
 |
Trusting Your Data: Garbage In, Garbage Out Poor quality input will always produce faulty output. Improper validation of data input can affect more than just security; it can also affect your ability to make effective business decisions. Bad data can have impacts on how you make quantitative decisions or create reports, if you can’t trust the data you receive. |
|
 |
Lessons Learned from Product Failures Being agile is all about learning from failures and building on experiences. This applies to not just individuals, but even to large organizations. The key is being transparent and objective in accepting and understanding failures, and taking away lessons for future actions and decisions. Just keep innovating. |
