Organizations of all kinds are increasingly adopting user centered Design Thinking practices instead of sitting around boardroom tables with their peers, dreaming up the next big feature or digital product they think their users need. But depending on your company culture and organizational structure, you may still be finding it challenging to break the “grand assumption” habit.
Tim Siemens is the Chief Technology Officer with Online Business Systems. We asked Tim to share his insights with us on the top 3 technology trends in 2018.
Do I Really Need a Business Case?
A completely legitimate answer to this question is “no”….BUT only if you have a lot of time, money, and people - and a desire to waste all three!
|A business case:
A business case, at the very least, makes one think more carefully about a future initiative. At its best, a business case helps ensure an organization is undertaking an initiative that will add value, which includes being in alignment with organizational goals.
Another benefit of writing a business case is that it sets the parameters for the initiative, which then feed into the project planning process making it easier for the project sponsor and project manager to move the initiative forward.
Principle # 1 – Use a “benefits-led” approach
In my previous post, “Why Benefits Should Drive Your Project Planning and Delivery”, I introduced the concept of adopting benefits management so that benefits can be properly planned, delivered, and measured. As a key principle of benefits management, I also shared how adopting a “benefits-led” approach to program and project planning can improve successful project delivery, so that the intended business outcomes are achieved and their expected benefits are realized.
Topics: Project Management
Over the past decade, the level of attacks, breaches, and potential dangers to vital data have escalated to the point where organizations in every industry need to take measures to ensure their assets and technical infrastructure are safeguarded. A key part of that protection is having the continuous knowledge of where your environment is vulnerable and the type of risks that may threaten it. The approach you take to continuously monitoring for threats and vulnerabilities can vary based on a number of factors, such as existing technology, staffing, and internal processes. Not to mention the financial impact based on your organization’s resources and maturity. This leaves you with several critical decisions your organization should consider when determining an in-house, or outsourced approach to security operations.
In Part One of my blog series aimed at breaking down each section of Online’s security policy, we looked at some general best practices surrounding the development of a security policy. This included answering the question of “why develop a security policy?” and went into detail about developing the scope of content contained within. Part Two analyzed the organizational roles and responsibilities needed to implement an effective security policy. Now let’s take a look at how Electronic Communication plays into an effective policy.
With Christmas trees getting wrapped up for the chippers and the feelings of celebration, togetherness, and giving diminishing to their normal levels— comes that familiar feeling of buyer fatigue. Whether we’re questioning the impact or necessity of the gifts we gave, wondering if we’ve gone overboard or are simply just happy that all the running around is over. A lot of us are just feeling tired at this point in the season. Tired of just buying… stuff.
As you may have heard in the news, computer researchers have recently discovered a design flaw that results in a security vulnerability in the CPU chip that powers nearly all the world’s computers, including PCs, smartphones, and data center computers. This hardware bug allows malicious programs to steal data that is being processed in the computer memory. The name given to these vulnerabilities is ‘Meltdown’ for Intel chips or ‘Spectre’ for AMD and ARM chips. The first reports were published on January 2, 2018, prior to a coordinated disclosure scheduled for the week of January 8. There is no evidence of exploitation at this time, but the publicly disclosed proof-of-concept (PoC) exploit code could result in the vulnerabilities being weaponized for malware delivery.
As 2017 comes to an end, the latest PCI DSS 3.2 requirements (coming into effect on Feb. 1, 2018) are on the minds of many Service Providers and Merchants. A natural question stemming from these changes is "What do I do if I fail my PCI assessment?" Let's take a look back to a blog written earlier this year that answers just that.
Remember when PCI DSS version 3.2 was released way back in April 2016? We counted our blessings that the new requirements truly raised the bar - especially for Service Providers - and gave us a considerable grace period to implement them. And as it goes, 2018 seemed so far away and implementing these changes didn’t seem so urgent. Well fast forward to today and all of a sudden January 31, 2018 doesn’t seem too distant in the future anymore.