Jump to content

Jimi Wikman

💫 Owner
  1. Over the past few decades, securing remote access has become monumentally more complex. Remote work, with all of its benefits, has also furthered the threats of shadow IT and unauthorized remote access. Companies now need to secure their systems by guarding five pillars: identities, applications, devices, data, and networks. Even so, there’s a gap between the people, devices, and applications that we trust to access sensitive data, and those that actually do in practice (this is called the “Access-trust Gap”). As such, we created 1Password Extended Access Management® to give companies complete visibility and control over the user identities and devices that access their resources.
  2. While there are plenty of bugs still in Invision Community V5, they are not bad and compared to the state of this site right now it is still a big improvement. I am still waiting for the next Beta to come out though as there is a bug with the Tags that I want to have fixed before I switch over. Once that is fixed I will most likely switch over and start working on the site again. When I switch over things will be very messy for a while, but that is expected. I will basically revert all customizations and then start over with the V5 engine to redesign certain templates. Right now I am saving all the templates as code for safekeeping, and so I can check what customizations I have done in the past. Once I have that I will make a fresh export to the beta site with the production data and production files. Next step is to change the templates for all databases to the default ones. I will then delete the old template files to make sure there are no customizations anywhere that can cause problems. After that I will do a V5 upgrade and if all goes well then I will just wait for the next Beta release to get the Tags bug fixed before I upgrade the production site. Once everything is upgraded I will start configuring everything. I will focus on the Articles, Stories and Atlassian Product Updates since those are the ones I will work with most after the upgrade. After that I will probably take a look at the My Projects database, Videos database and then the Atlassian CVE's. This can all change depending on what I see I need to focus on next.
  3. An excellent article that illustrate that there are many people today that are so focused on working with user stories, that they have completely forgotten that requirements are not user stories. User stories are the outcome of the requirements.
  4. The conference room falls silent. The projector hums quietly, displaying yet another requirements document that will likely join thousands of others in the corporate graveyard of unused solutions. Somewhere between “The system shall” and “User acceptance criteria,” we’ve lost sight of what truly matters. Requirements aren’t working anymore. Here’s why — and more importantly, what should replace them.
  5. After more than a decade only having my company phone and company laptop I have decided it is time to make a change. The last few years have been very stressful and not having the clear boundaries between work and private life have caused some issues. I also feel it is time I take ownership of what is and is not mine and to feel secure that I am at the mercy of my company when it comes to my data. My first step was to buy a new laptop. I already have a stationary computer, but I enjoy watching movies, write and do some coding on a laptop. As I don't need anything really powerful I bought a Samsung Galaxy Book4 i7-1355U/16/512/IPS 15.6". It should be ready to pickup later today, or tomorrow. Tomorrow I will also go get myself a new phone. It will be another iPhone, and I am not really picky if it will be a iPhone 15 or iPhone 16. I'll just take what is in store since they are fairly similar in terms of what I need. I feel that this separation will allow me to better manage my time and make a clear separation between what is mine and what belongs to the company. I can now put away the work at the end of the work day and pick it back up again at the beginning of the workday. I think this is extra important when we work in hybrid or remote settings as there is no longer that sense of walking out the office door to help with the distinction between work and private life. I am looking forward to this, and I can't wait to get my new "toys" so I can start setting them up just the way I want them to be!
  6. As I am taking my farewell of Sinch after two years of working with all of you, I do so with mixed feelings. On one hand I am excited to start new adventures next year, but on the other hand I will miss working with all you amazing people at Sinch. Over the past two years we have accomplished amazing things together. Despite it being very hard for you sometimes to adjust to the more structured and limited ways of a controlled platform, you have accepted the change with respect and enthusiasm. In a typical Sinch way you have taken the lemons and turned them into lemonade, and you have done so with positive energy and curiosity. For every obstacle you have come up with a dozen solutions and when in doubt you have fearlessly asked questions. It has been a true honor working with such amazing people as you are. Even in a time of endless changes you have surfed the waves and anytime anyone of us have fallen, we have helped each other up to try again. We have worked together across timezones, cultures, religions and experiences to build a better Atlassian Experience, and I am in awe over your dedication towards this end. Not just for yourself, but for everyone at Sinch. While I will no longer be there to guide you towards the next destination, I am confident that the foundation we have set together will get you there and that the future will be glorious for all of you. While I technically will not leave Sinch for a few months yet, I wish you all the best and I can't wait to see where your Atlassian Journey takes you next or what wonders you will create using the Atlassian platform. I will miss you and I wish you all the best.
  7. What is a deadline? For some, it's a secret line that should never be crossed but only quietly approached and quickly completed. For others, deadlines exist, but somewhere indirectly - if I have time to complete the task, I will. If I don't make it, nothing terrible will happen. However, when working on a particular project, each task depends on the others; the overdue deadline for one issue can become a major blocker in the development. To never miss a deadline when using Jira, you'll want to effectively manage and monitor time, status, and other relevant metrics.
  8. Ineffective communication affects nearly half of all workers, presenting a common challenge: leadership messages that aren’t delivered clearly or efficiently. Improving top-down communication is essential to aligning everyone with the company’s goals and fostering collective progress. This article delves into what top-down communication entails, its common obstacles, and effective strategies for improvement.
  9. Do you ever create several different diagrams on a Confluence page and find yourself constantly leaving the Gliffy editor to update each one separately? Want a way to sketch your work in one spot and finalize it an another — without a ton of jumping back and forth? With Gliffy's new multi-page functionality, you can work with multiple diagrams at once by creating additional tabs—each one has the full functionality of the Gliffy editor. I've heard from our customers that we're great for complex, technical diagramming, so as Gliffy's PM I'm always looking for functionality and improvements that help you best handle that complexity. Really excited about this addition!!
  10. We've released the new Spaces feature to customers on all editions! This is a new location where product admins are able to manage and take action on their spaces from a consistent, convenient location.
  11. We're excited to announce that the ability to edit a space key has now been rolled out to all customers (excluding those on release tracks)! How it works The technical approach that we are using will leverage two different keys: an internally generated ID plus an additional, separate key that is what will be shown to your users. This approach is represented in the UI as: System space key = internally generated ID Space key = the visible alias that's seen by your users
  12. Some time ago, there was a webinar recorded by VersionOne: How to use SAFe® to Deliver Value at Enterprise Scale Q&A Discussion with Dean Leffingwell). If you fast-forward to about 23 min, 20 seconds into the recording, you will hear the following statement: “…We don’t typically mess with your organizational structure because that is a pretty big deal…” This statement somewhere puzzled me. While graphic representation of SAFe framework is nowhere short of supporting organizational complexity, I was still under impression that organizational design improvements/simplification are included in SAFe teaching. To me, an ability to influence first-degree system variables, such as Organizational Structure, is critical. Without this ability, any attempt to improve organizational agility and system dynamics would be short-term and limited. Even such important second-degree system variables, as organizational culture, values, norms, behaviors, policies, agile engineering practices usually bring limited results if organizational structure remains unchanged.
  13. In any project or team, tracking the efficiency of issue resolution is key to improving productivity and identifying bottlenecks. This week’s report offers a detailed visualization of how issue resolution performance has evolved over time, allowing teams to gain actionable insights into their workflows. Let's break down what this report reveals.
  14. Cycle time is the amount of time it takes for a task to move from the start to the finish line. In Agile, cycle time helps teams see how quickly they can deliver value to their customers while finding ways to do things faster without sacrificing quality. Cycle time usually complements two metrics: lead time and throughput. While lead time measures the total time from when a request is made until it's delivered, cycle time focuses only on the active work phase. Throughput, on the other hand, looks at how much work is completed over a certain period.
  15. The Role of Cybersecurity in Medical Device Safety The Global medical device market is a $800 billion business that is rapidly growing, especially in the area of software as a medical device (SaMD). The majority of the SaMD segment is made up of the digital health and digital therapeutics solutions, where medical devices are made solely of software.