Jump to content
Search In
  • More options...
Find results that contain...
Find results in...

JimiWikman

©Owner°
  • Content count

    848
  • Joined

  • Last visited

  • Days Won

    10

JimiWikman last won the day on June 22

JimiWikman had the most liked content!

Community Reputation

29 Excellent

About JimiWikman

  • Rank
    Just Arrived
  • Birthday 07/27/1974
  1. Announcements in Jira is an important part of the Jira administrators job. The balance between being annoying and not keeping the users properly informed is a thin line indeed. While Jira provide email and banner options, its still a blunt tool to use and sometimes you even wish for your Jira Project Leaders to have the power to keep their projects informed. This is where Announcer for Jira can help. With it's flexible system it can inform users in many ways, including group selection, scheduled notifications, several types of notifications and more you can make your notifications as unobtrusive as your users need them to be. It's quite the tool to add to your arsenal of plugins and during upgrades and incidents your users will love you for giving them the power to be informed.
  2. Planen är att ha minst 4 events varje år och frågan är vad vill ni se och vilka system vill ni att vi fokuserar på?
  3. JimiWikman

    Jira Upgrades - best practices and best tips

    until

    Vi tappade själva uppgraderingen på grund av tekniken vilket var lite synd. Ett bra event annars, men lite för kort tid för planeringen så vi inte riktigt hann med att förbereda. Mycket trevlig lokal och Riada var som alltid toppen 🙂
  4. until
    Join us at Riada HQ, at Vasagatan 36, for a hands-on upgrade of Jira along with best practices and the best tips and suggestions for making the upgrade as easy and painless as possible. Afterwards we open the floor for questions and general discussions regarding the Atlassian Eco-system.
  5. Join us at Riada HQ, at Vasagatan 36, for a hands-on upgrade of Jira along with best practices and the best tips and suggestions for making the upgrade as easy and painless as possible. Afterwards we open the floor for questions and general discussions regarding the Atlassian Eco-system.
  6. Just curious to see who is going to the summits and who is not 🙂
  7. JimiWikman

    Atlassian Summit 2018 - Europe

    until
    The world's next best innovations will be built by teams like yours. This is why our mission is to help unleash the potential in every team and why we hold Summit year after year. Join our team along with other users to be inspired, hear expert advice on the best ways to use Atlassian tools, learn about the latest technology and product updates, and celebrate the teams that make the world a better place. Give your product skills a major boost and earn your certification. Choose from courses ranging from beginner to expert. Learn more Partner Day Join Experts, Marketplace Vendors, Corporate Resellers, Training Partners, and Affiliates for a special day. Learn more Industry User Groups In the automotive, finance, legal, or service industry? Connect with teams like yours to painpoints and best practices. Learn more ShipIt Live Witness teams race against the clock to ship an amazing project and vote for your favorite hackathon winner!
  8. Confluence have many uses, but what do you use Confluence for?
  9. Many want a chat on their site, what are the selling points for just liveChat since there are so many different services for this?
  10. Tired today, but feeling good.

    Really need a vacation soon, so I am looking forward to that in a few weeks.

  11. This month saw two significant milestones in the WordPress community — the 15th anniversary of the project, and GDPR-related privacy tools coming to WordPress Core. Read on to find out more about this and everything else that happened in the WordPress community in May. Local Communities Celebrate the 15th Anniversary of WordPress Last Sunday, May 27, WordPress turned 15 years old. This is a noteworthy occasion for an open-source project like WordPress and one well worth celebrating. To mark the occasion, WordPress communities across the world gathered for parties and meetups in honor of the milestone. Altogether, there were 224 events globally, with a few more of those still scheduled to take place in some communities — attend one in your area if you can. If your city doesn’t have a WordPress meetup group, this is a great opportunity to start one! Learn how with the Meetup Organizer Handbook, and join the #community-events channel in the Making WordPress Slack group. Privacy Tools added to WordPress core In light of recent changes to data privacy regulations in the EU, WordPress Core shipped important updates in the v4.9.6 release, giving site owners tools to help them comply with the new General Data Protection Regulation (GDPR). It is worth noting, however, that WordPress cannot ensure you are compliant — this is still a site owner’s responsibility. The new privacy tools include a number of features focused on providing privacy and personal data management to all site users — asking commenters for explicit consent to store their details in a cookie, providing site owners with an easy way to publish a Privacy Policy, and providing data export and erasure tools to all site users that can be extended by plugins to allow the handling of data that they introduce. To find out more about these features and the other updates, read the 4.9.6 update guide. You can also get involved in contributing to this part of WordPress Core by jumping into the #core-privacy channel in the Making WordPress Slack group, and following the Core team blog. Updates to the WordPress.org Privacy Policy In a similar vein, WordPress.org itself has received an updated Privacy Policy to make clear what is being tracked and how your data is handled. Along with that, a Cookie Policy has also been added to explain just what is collected and stored in your browser when using the site. These policies cover all sites on the WordPress.org network — including WordPress.org, WordPress.net, WordCamp.org, BuddyPress.org, bbPress.org, and other related domains and subdomains. It’s important to note that this does not mean that anything has changed in terms of data storage; rather that these documents clarify what data is stored and how it is handled. Further Reading: WordCamp US 2018 has opened up speaker submissions for the December event. Live stream tickets are now available for WordCamp Europe, happening on June 14-16. Gutenberg, the new editor for WordPress Core, is getting ever closer to the final stages with a major update this month. In preparation for Gutenberg, significant work has been done to improve WordPress Core’s build process. If you have a story we should consider including in the next “Month in WordPress” post, please submit it here. View the full article
  12. Jira Introduction for Jira Project Leads Welcome Project lead, to a brief introduction to Jira and your responsibilities and options as Jira Project Leader (JPL). As JPL you are responsible for all activities within your projects. This includes all on-boarding and off-boarding processes as well as making sure your project is maintained in a way that ensures that no performance impacts can occur. As your responsibility is quite big, you are also eligible for training and support. Responsibilities The JPL have full responsibility of his or her project. This means that anything happening within the project will fall on the JPL. This includes performance issues due to wrong setup or usage of fields, flows, boards and filters. It also includes on-boarding new users and of course off-boarding to ensure that no users that should no longer have project access still linger within your project. As the JPL you are also responsible for ensuring that your team or, teams, can work in an optimal way. This includes helping them to setup and operate boards, sprints and so on. You may not be the person who actually do this on a day to day basis, but you need to know how to support the members of your project should they need it. You are also responsible to ensure that the project specific functions for versions and components are maintained correctly. That includes to archive versions no longer being used and ensure that the setup of components are used according to standards to allow for cross functionality and integration sanity. Contact person The JPL is the first contact, and often only contact, when issues occur in Jira. As the contact person the JPL is required to be a member of the Jira Teams as well as keeping updated regarding news on the Jira SharePoint site. In the event of an issue with Jira as a whole, or even more important an issue with the project the JPL is responsible for the JPL should be able to respond within a reasonable time frame. Failure to respond could lead to a shutdown of the project. If a JPL is no longer active the project can be shut down until a JPL is assigned. This is because we cannot have a project without a responsible person owning it. A person must be contactable should anything happens that require action from the JPL. On-boarding a Project On-boarding a project is done by making sure the correct setup has been added during creation. This is done by accessing the project settings and reviewing the settings. If the settings are not correct it could cause serious problems working in Jira for the whole team. During the project creation it is also up to the JPL to verify that the workflows and other settings are not only correct, but also suitable for the team to work with. If the way of working can benefit from customization than this can be discussed with the Jira team. Customizations are exceptions and require an obvious improvement to the workflows of the team. Off-boarding a project When a project is no longer needed it need to be archived. This is done by sending a request to the Jira team. Doing this will make the project read only for a year and then hidden for a year before it is deleted. When a project is archived it will no longer show up in searches. All issues in the project will also be hidden from searches. This reduce the number of items that show up in searches, which in turn will reduce the number of items that need to be fetched from the database. This help performance and reduce clutter in Jira. Handling Users Handling users is done by adding or removing users manually in the Roles section. When a user is added to the Jira project it is the responsibility of the JPL to ensure that the users have the knowledge and understanding of how to work in Jira. As the JPL this responsibility cannot be put of someone else and if a user cause incident in Jira due to not understanding the way of working or how Jira works, that is on the JPL. For this reason, it is suggested that new members get proper training within the project or by attending a Jira training session. Each user uses a license in Jira and as such it's very important to not let users accounts remain after they have left. It's the JPL who is responsible for keeping their members up to date as they also are responsible for the license cost of their project. Handling versions Versions are important parts of Jira as it is the way we can determine in what code base development or configures has been committed. Version are created and managed by the JPL and project managers, which means that the responsibility with releasing and archiving versions also fall on the JPL. Once a version no longer is required to connect defects to that version should get closed. This is done by the JPL and the project managers. If this is not done properly the list of versions will grow exponentially, which causes issues for the project and potentially for Jira as a whole. Handling Components Components are used for additional grouping for Jira issues within a project. While this is a very useful feature it's also important to remember that components are project specific and if you work cross projects then a moved issue can lose this information. It is the responsibility of the JPL and the project managers to manage the components and make sure it's used on a level that cannot be compromised if an issue moves to another project. For this reason, components should not contain issue critical information. Performance impact decisions Decisions within the project, like adding new custom fields or values within a custom field, custom workflows or filters for boards also fall under the responsibility of the JPL. For this reason, it's important to understand the impact new fields, filters and so on have on the project as well as on Jira as a whole. Should a project become slow due to performance issues or worse, if all of Jira would suffer due to decisions that lead to performance issues, that is on the JPL. For this reason, it's no excuse to claim ignorance as failure in this regard can cause severe impact and possibly legal actions. As JPL it is strongly suggested to consult the Jira team if you wish to adjust your project that you are unsure if it can impact performance. Expectations Day to Day operations The JPL should have knowledge on how to do the basic day to day operations. This includes creation of sprints, setting up boards, working with filters and backlogs as well as the JPL specific tasks of managing components and versions. The JPL are the owner of your project and as such the JPL should know how Jira works so they can guide the members of the project on a daily basis. The JPL are not expected to be an expert but should know the basics. For this reason, all JPL's should attend the JPL training before starting their project. It's also suggested to attend at least one JUT training session and all JST training available. Possibilities While it might sound like a JPL have a lot of responsibilities they also have a lot of possibilities. Not only will the JPL have access to the JPL trainings, they also have the possibilities to request support and guidance from the Jira team. Training Besides access to the JPL training sessions all JPL's have the option to request support from the Jira team for specific training sessions. This can be anything from an extra JUT session or it can be a full-fledged JST with custom content specifically designed for the need of the JPL and the project team. At any time can the JPL request assistance on Jira matters from the Jira team through Teams. Jira Customization All projects are not equal, but in Jira they all follow the same structure. For this reason, it is sometimes necessary to make customizations to improve the quality of work or improve efficiency. The JPL can request a consultation with the Jira team to discuss a solution to achieve this that is best suited for the project as well as for the system as a whole. Common requests are custom fields to add more information inside Jira, custom workflows for situations when the standard flows no longer apply and custom screens for displaying certain type of information differently. Since these requests cause a strain on performance they need to be carefully considered and designed so they can be used by many and not be project unique only. All customizations must be requested by the JPL and it must be approved by the Jira team before it can be added to the system setup. Plugins Plugins is a special request that also can be initiated by the JPL, but as plugins have a much higher degree of maintenance it cannot be approved by the Jira team alone. All plugins follow the demand process where it will go through an approval board. It is up to the JPL to define why a plugin should be added to Jira and to secure the finances to pay for it.
  13. In 2015, ABN AMRO, one of the largest banks in the Netherlands, rolled out agile across their organization. Within a year and a half, ABN AMRO grew from over 100 to 7000 users, and they are now moving towards using JIRA Software Data Center. This growth greatly increased their system complexity, that included 65 administrators that had created over 65 issue types, 250 statuses, and 400 workflows. In this session, ABN AMRO will share the process of introducing scaled agile to their organization, which includes identifying the impact on usability, gathering metrics, and improving system performance and maintenance. You can also learn about how Portfolio for JIRA is an integral part of scaling agile across an organization and which best practices you can apply to your own journey.
  14. It's no secret that scaling agile is a challenge both culturally and operationally. So, how do other companies do it? How do they achieve success and what do their journeys look like? Bree Davies, Portfolio for Jira Product Manager, will detail one such case study of how a large insurance company with 12 software teams collaborate, plan and track their work to deliver value to their customers continuously. You will hear about a company's transformation to scale agile and how tools such as Jira Software and Portfolio for Jira have been key to their operational and cultural success. Plus, you'll walk away with tips and tricks to use Portfolio for Jira efficiently for your own long term planning.
  15. The WordPress.org privacy policy has been updated, hurray! While we weren’t able to remove all the long sentences, we hope you find the revisions make it easier to understand: how we collect and use data, how long the data we collect is retained, and how you can request a copy of the data you’ve shared with us. There hasn’t been any change to the data that WordPress.org collects or how that data is used; the privacy policy just provides more detail now. Happy reading, and thanks for using WordPress! View the full article
here
×