• Best Practices in Jira – Dashboard Reporting

    9 September 2020
    Comments are off for this post
    Best practices in Dashboard Reporting for Jira

    Introduction

    Jira Dashboards is a very powerful feature if used correctly. In this article, we will share with you the common pitfalls as well as some best practices based on our experiences as an Atlassian Solution Partner. 

    Why people use Jira Dashboards 

    Dashboards can be from a macro perspective like % of project completion to micro level on the list of tasks with their statuses. 

    Some common use cases for Dashboards are:

    • monitor the progress of the tasks
    • track the KPIs and the health of the project
    • highlighting important stuffs (e.g. SLA breach, bottlenecks, shortages) for action taking
    • show progress to motivate the team

    More organisations are preferring dashboards over reports because of the following reasons:

    • live information – able to see the current status which is more accurate
    • time saving – there is no need for someone to spend time to compile the weekly/monthly progress reports manually
    • interactive – as compared to a chart image in a PPT/PDF
    • allows drilling in – you can zoom into the details of the issue for more information
    • self reinforcing – it encourages people to update their Jira issues regularly

    Common pitfalls and recommendations

    Security / Information Disclosure

    From our Jira consulting experiences, there are a number of instances where the dashboards and filters are accessible by users without logging in.

    Although Jira’s permission scheme will prevent public users from viewing the issues, it is still possible to disclose sensitive information which may not be meant for public eye.

    Information can be disclosed due to Jira filters shared with anyone on the web

    You should check whether there is information disclosure by logging out of Jira and visiting the URLs

    • Dashboards – https://<jira-base url>/secure/ManageFilters.jspa
    • Filters – https://<jira-base url>/secure/ConfigurePortalPages.jspa

    Unless the dashboards/filters are for public access, users should not select Public for the Add Shares option.

    Edit Jira filter screen

    Tip: There is a “Sharing with anyone on the web” in Jira configuration which you can disable to remove the Public option if your Jira instance is not for public access.

    Disable allow sharing filters/dashboards with anyone on the web

    Performance and utility

    Another common pitfall is people tends to create 1 dashboard for each project and cramp everything inside. We have seen a dashboard with over 20 gadgets added. As a result, it clutters the dashboard and is slow because it has to load a lot of information. This can also slows down the Jira instance for other users.

    From a design point of view, this is bad because it introduces a lot of noise in the dashboard. As a result, people cannot zoom into the important things that they need to take action from the dashboard.

    A well designed dashboard should fulfil the following:

    • Targeted for the role/purpose – A management report should not include the micro information like the list of tasks. Likewise a developer will be more concerned about the list of tasks he needs to work on. You can create different dashboards for different roles.
    • Incite emotion or action – it should bring attention to the readers to take any necessary action. With correct use of colours and placement, users can determine the severity easily.
    • Easy to understand – It should use the correct type of gadgets to present the information in the most direct manner. You can check out the list of Jira gadgets available on Atlassian Marketplace.
    • Responsive – it should be fast to display the information without the reader having to scroll through many screens to read the entire page.

    Discoverability

    A dashboard is useful only when there are people using it. Another common pitfall we observed is that every user tends to build their own dashboards. While this is flexible, there are some disadvantages like:

    • duplicated effort to create and maintain the dashboards
    • decreased utility since only 1 person is using it
    • some users are unaware on the types of gadgets available that they can use for reporting
    • some users lack the proper training on how to write complex JQL queries and design good useful dashboards
    • no standards on the performance metrics to monitor within the organisation

    To tackle this, we advocate to design a set of dashboards as a template for every Jira project. When a new project is created,

    1. the set of dashboards and filters are also created based on the template
    2. The filters and dashboards are shared with the project so that people who have access to the project can access them
    3. Then the dashboards/filters are added to the Jira’s project shortcuts where all project members can access easily
    4. They can also be added to the Dashboard Folders and Menu Gadgets so that users can easily navigate to the reports
    Dashboard folders allow dashboards to be accessed directly from Jira

    Maintainability

    Another common problem that Jira admins face is obsolete dashboards/filters. By default, only the original creators can edit their dashboards/filters.

    From Jira 7.12 onwards, it is possible to grant permissions for other team members to edit filters/dashboards. Hence a useful tip after creating a filter/dashboard will be granting permissions to the associated project roles

    • to grant view permission to all project members
    • to grant edit permission to the project administrators
    Set view and edit permissions to project roles

    Naming Convention

    We also recommend to define a naming convention for filters and dashboards. E.g <Jira project key> – <purpose>.

    This is especially helpful for users when they are searching for a filter when configuring the gadgets. For very large instances, you can find multiple filters with the same name while selecting a filter for a gadget.

    It is possible to define aliases for dashboards and filters with Dashboard Folders and Menu Gadgets.

    System Dashboard

    When a user adds a new dashboard themselves, the system dashboard will disappear.

    Actually the System Dashboard is very important because it is tedious to go through the list of project dashboards.

    The System Dashboard can complements by

    • providing a consolidated view and highlight the important things that matters to the user
    • as well as a landing point where the user can navigate to other places

    Conclusion

    In conclusion, here is a checklist that you can use:

    1. review the list of public dashboards/filters and decide whether to disable public sharing
    2. set editing permissions for the shared dashboards
    3. define a set of dashboard templates for your Jira project
    4. define a naming convention for dashboards and filters
    5. install apps from the Marketplace that you identified that are useful

    If you like this article, you might be interested to check out our best practices series

    Share this post

  • Best Practices in Jira Administration – Be a Jira Hero ebook

    27 May 2020
    Comments are off for this post
    Be a Jira Hero ebook

    This is an ebook on a collection of Jira best practices that Atlassian has gathered from Jira experts around the world.

    The title “Be a Jira Hero – A guide for Admins, by Admins” is well deserving. Therefore we recommend all Jira administrators and wannabes to read the 25 pages ebook.

    Jira Best Practices ebook

    The ebook is well-organised into different sections with short but clear snippets of wisdoms:

    1. How to keep Jira clean and simple for your users
    2. How to use issues effectively
    3. Best practices on managing Custom Fields and Screens
    4. Things to consider when building workflows
    5. Tips on managing backlog in Jira
    6. How to get people to work on the issues
    7. Best practices on designing the Jira dashboards for even more effective reporting
    8. Shortcuts & Hacks to work faster with Jira
    9. How to make use of automation to make life easier

    One Common Mistake

    For example, the book has highlighted in Tip #20 to incorporate Resolution into the workflows. We observed that a number of Jira admins who did not have formal training tends do not understand the concept of resolution. Consequently, they overlook this important step while creating new workflows. While the Jira appears to be working, the implications are some built-in reports may be inaccurate and an important piece of information is missing.

    Our Additional Jira Tip

    Dashboards are very useful if they are used correctly. Team members can have visibility on the progress and be reminded on the outstanding tasks. Furthermore, Management can have clear visibility without spending a lot of time preparing routine reports. As a result, users will understand the value of updating their tasks in Jira.

    Horizontal Bar Chart for Jira
    Multiple Filters Statistics Bar Chart Gadget
    Horse Shoe Gauge Gadget for Jira
    Horseshoe Gadget Jira

    Conclusion

    To sum up, if you are a Jira administrator, you should download the ebook and review whether you have been applying the Jira best practices.

    There is no need to provide any email address to download the book. To add on, you may also want to check out the following resources:

    Share this post

  • Best Practices in Jira Administration – Jira Apps Management

    5 May 2020
    Comments are off for this post
    Atlassian Marketplace in 2013
    Screenshot of Atlassian Marketplace in 2013

    This is a “lengthy” guide on the best practices on choosing and managing a Jira app. Coming from our years of experience as an Atlassian Solution Partner, it covers

    1. How to evaluate a Jira app
    2. How to better manage the apps installed in your Jira instance
    3. Things that Jira administrators need to watch out

    Jira Apps from Atlassian Marketplace

    By installing additional Jira apps, you can add new features to your Jira. For example, some of our popular Jira apps

    There are many more useful Jira apps available at the Atlassian Marketplace.

    Evaluating a Jira App

    Being an Atlassian Solution Partner, there are a number of criteria that we consider before recommending a Jira app to a customer. They are:

    Fit to Purpose

    The app should be able to address the requirements fully. It should be easy to use. The additional feature should not cause confusion to the existing users. We will also assess their design is robust and does not conflict other plugins or use cases.

    Atlassian Marketplace Listing

    Best Practices on Multiple Filters Chart Gadgets Marketplace Listing

    It is very important to check out the app listing on Atlassian Marketplace. It contains a lot of useful informations like

    • Rating and Reviews
    • Number of Active Installations
    • Vendor Accreditation
    • Compatibility with the latest version of Jira
    • Support

    Rating and Reviews

    While the rating and reviews do not mean much for a newly listed app, they do give insight of poor services or badly designed apps. Typically, users will flag out any issues that require attention. So, if there are no negative reviews, it is safe. And if there are a number of good reviews, then it is very safe.

    Number of Active Installations

    If an app is popular with a significant number of active installations, that is a good sign that the app is useful and functioning without major issues.

    Vendor Accreditation

    Atlassian has a Top Vendor program who has met the following requirements

    • App traction – Their paid apps must attain at least 500 active installations
    • Timely support – Has a Service Level Agreement (SLAs) and committed to provide at support for their users
    • Support Website – Customers can raise support request easily via a website or email when necessary
    • Vendor reliability – Atlassian conduct checks periodically to ensure they offer great customer experiences

    For those exceptionally good ones, they are further recognised as Gold/Platinum Top Vendor.

    Versions compatibility

    If the app is only compatible with an older version of Jira, that is a big warning. You do not want to be left dangling helplessly for your next Jira upgrade.

    Support

    Some apps are explicitly marked as unsupported. Unless you can accept the risks, it is better to avoid them.

    Data Center Approved

    Data Center approved apps are those that have passed Atlassian’s stringent criteria for use in Jira Data Center environments. As it takes considerable effort to become a Data Center Approved App. vendors will usually do that for their established apps. Therefore this is a plus point.

    Thorough Documentation

    Although some users will usually dive in without reading the user guide, it helps when the documentation contains

    • A quick overview of the functionalities
    • Comprehensive writeup and how to use
    • FAQs to facilitate on-boarding and best practices
    • Up-to-date release notes
    • An easy to navigate structure

    Unless the app is really simple or open source, it is a risk to install an app with a one pager documentation.

    Pricing

    Last but not least, the pricing of the app is also an important consideration. The app should have a reasonable pricing so that you will be assured of support for long term. It is also possible that you will upgrade to higher user tier or Data Center as Jira becomes an enterprise application. Hence the pricing for higher tiers should not exceed your budget.

    For free apps, they should be from a credible publisher with significant number of installations. Otherwise, the publisher may withdraw support in near future.

    Before Installing an App

    Downloading the compatible version

    There is a common mistake for Jira administrators who are unable to download the app via the Atlassian Universal Plugin Manager. The default download link on the Marketplace listing is for the latest version of Jira.

    If you are not using the latest version of Jira, the correct steps to install/upgrade the app will be

    1. Click on the Versions tab
    2. Select See all … versions
    3. Hover on the topmost version which matches your Jira version
    4. Click on the Download link
    5. Upload the file via Atlassian Universal Plugin Manager in Jira

    Testing

    It is a best practice to install the Jira app on a Test environment first. It is not advisable to install an app directly onto the Production environment. This is because some apps may make changes to the database. Some changes are not be reversible when you uninstall the app later.

    Maintaining a Change Log for the Apps

    We usually advise our customers to create a Confluence page to track on the app installations, upgrades and uninstallation. This best practice helps to keep all the related information organised neatly on a single page.

    The change log table can include the following information

    1. Date of Change
    2. Changed By
    3. Name of App
    4. Action Performed (e.g. install/upgrade/uninstall)
    5. From Version
    6. To Version
    7. Jira Issue Key
    8. Additional Notes

    This will be useful especially when there are multiple Jira administrators who can perform changes. Although the audit log has a record of the changes, the default data retention period is only 90 days. It is also not that easier to read.

    By using a Change Log, the administrator can link the change with a Jira issue and add notes. The Jira request helps to identify the user who raised the request to install the app together with the background context.

    When there is an incident, the App Change Log will be useful to identify issues caused by app changes.

    Things to watch out

    It is not the end of the story after installing the app. There are a few useful tips for Jira administrators to watch out.

    Hardware Sizing

    With more apps installed, it is likely that the memory footprint might increase over time. It will a best practice to check on the JVM memory utilisation from the System Information page after people start using the features. Likewise, CPU usage monitoring is also a best practice.

    Expiring Licenses

    There are a handful of apps which will stop working without an active license. So be sure to renew your licenses before they expire to gain access to support and newer releases.

    Being informed

    You can click on the Watch app link on the Marketplace listing. By doing so, Atlassian Marketplace will send you an email whenever there is a new version released.

    Upgrading the Apps

    As a best practice, it is important to upgrade regularly to get newer features, performance improvements and bug fixes. For security vulnerabilities, you should upgrade as soon as possible once you received a security advisory.

    Scheduling Upgrades

    Although there is no need to schedule a maintenance downtime for installing/upgrading Jira apps, it is a best practice to do that during off-peak periods. During an app installation, there is a short interval where the Atlassian Universal Plugin Manager removes the old version and installs the newer version. You do not want any critical operations in between that period.

    Also some apps may execute jobs during the upgrade to do some data crunching to support a new feature. Therefore, please read the release/upgrade notes for the app before you click on the upgrade button in Jira.

    Share this post

  • How to integrate Sonatype Nexus Lifecycle with Atlassian Tools

    25 February 2020
    Comments are off for this post

    Introduction

    It is a fact that no software is built from scratch. Almost all of us are using 3rd party libraries to speed up the development lifecycle. Hence it is important to ensure that the open source components used are safe. Otherwise it could be the weakest link. This post introduces the possible integration between Sonatype’s Nexus Lifecycle and Atlassian toolset for DevSecOps.

    Sonatype Nexus platform addresses this challenge with earlier detection of security risks/non-compliance.

    Sandbox Application Build Report

    The products in the suite are

    • Nexus Lifecycle scans the open source components used and lists any reported vulnerabilities found. It also provides advice on which version is safe to use and the popularity of the open source components
    • Nexus Firewall prevents unauthorised/unsafe open source components from being downloaded from Internet to your artifact repositories like Nexus Repository or Jfrog Artifactory
    • Nexus Repository Manager caches the public components locally as well as storing the binary artifacts generated from CI/CD tools

    Sonatype is a market leader in this area because comprehensive coverage and higher accuracy (less false positives and less true negatives).

    Integrations

    Automated scanning during builds with Bamboo

    With the Nexus IQ for Bamboo app, developers can easily add a step to perform the IQ Analysis Task to the Bamboo build plan

    Sonatype Task in Bamboo

    Configure the Sonatype task in Bamboo

    With that, it is possible to see the scan results for each build. Developers can do comparison easily from the historical results from the Full Report link.
    The Nexus IQ server will only display the latest report for each stage of each application

    See the IQ Policy Evaluation results in Bamboo

    Policy Violation tracking using Jira

    Nexus IQ for Jira app can create Jira issues for selected policy violations.
    This allows the developer team to track the task easily and all the discussions and decisions are kept in context within the report.
    This reduces duplicate effort and speeds up resolution time by seeing how other teams solved the issue.

    Screenshot of Jira triggered by IQ Evaluation

    The organisation is clearly structured. Each IQ evaluation is a parent issue with each affected component as a subtask.

    A possible customisation will be to set the Affected Version(s) field.

    Policy Violation Overview in Pull Requests from Bitbucket

    The Sonatype Nexus Notifier for Bitbucket displays the Nexus Lifecycle policy evaluation information in pull requests.
    With this feature, the gatekeeper can ensure that the changes introduced meet the quality and governance guidelines before merging it to master.

    Display the Policy Violation found in Bitbucket

    Conclusion

    With the various integrations introduced, it is easier to ensure the delivery of quality software by empowering the developers throughout the various stage of development.

    Security should be everyone’s responsibility

    Share this post

  • Automating Tempo with ScriptRunner: Fast, Convenient, Efficient

    4 December 2019
    Comments are off for this post

    This is a guest blog from our partner – Tempo.

    Automation in Tempo is easy with the help of a tool like ScriptRunner! The team recently joined forces with Adaptavist and released 5 productivity scripts to automate parts of the process within the Tempo Suite. Today we’ll go over some use cases and scenarios for some Tempo ScriptRunner scripts. That being said, you can learn to automate some parts of Tempo and Tempo Timesheets in the automation webinar happening on December 5th with our partner Adaptavist.

     

    Never heard of ScriptRunner or Tempo? Time to elevate your game!

    ScriptRunner, one of the top apps on the Atlassian Marketplace, enables you to extend, automate, and customize your Atlassian stack via your own scripts or through some premade ones.
    Tempo, another top app on the Atlassian Marketplace, provides efficiency and visibility-enhancing apps such as Tempo Timesheets, Tempo Planner and Tempo Budgets to help IT, software development, consultancy, and business teams work smarter.

     

    Why should you care?

     Automating parts of Tempo enables added customization and simplification of the tool without creating recurring steps for your team. In other words, the user or team lead looking to perform specific actions from Tempo will not have to manually perform those actions anymore. By leveraging the pre-written scripts offered in the Tempo ScriptRunner Library, those actions will be automatically done!

     

    Today’s example: Get Tempo Plans Using the REST API for a Set Time Period

    This script uses Tempo Planner, a tool to streamline the management of teams and resources to quickly find available team members and maximize your resource utilization. As the name of the script suggests, ScriptRunner now has a way to remove some pesky manual labor and automate the process of pulling Tempo plans of interest for a given Jira Issue.

     

    Where does this script shine?

    Let’s take the case of Taylor, a team lead for Rougetech. Every month, Taylor and her team get together for their monthly planning. In it, they plan time for each team member on the tasks that they must do.

    In other words, her current steps to see the total plans for the next 4 weeks are as follows:

    1. In Jira, navigate to Tempo Planner and plan the task for the team
      Plan time for the team using Tempo

      In your Tempo Planner page, you will have the possibility of filtering the view to your team. The capacity of the team and the individual members will be displayed for the determined period.

    2. After the planning has been completed, Taylor will be able to revisit an issue to see who all the collaborators are, and quickly calculate the total time planned to see if it matches her initial prediction and budget.

      Planned Time for collaborators for Tempo

      The issue “Have Fun!” showcases all the planned time under “Collaborators”

     

    That being said, this is slightly annoying for Taylor because of the following:

    • She has to manually sum the time to find out how much time has been planned on the issue
    • It does not say when that time is being planned for as the issue shows the total planned time only

    On the surface, this might not seem like much and it could end up simply saving 5-20 minutes per issue. But, let’s not forget the following:

    1. Taylor has to look at more than one issue every month, making her waste even more time
    2. Taylor has to do the same steps over and over again when they can be automated
    3. Taylor has no idea if all the planned time is evenly broken up or if it’s all planned during a certain week

    This repetition of a mundane task could also be a widespread practice throughout the whole organization. Other team leads could be following the same practice (especially if it is standardized), meaning that the company is losing hundreds, if not thousands of dollars on such a little thing.

     

    In other words, the script does the following:

    • Reduces the amount of manual labor necessary to attain the end result
    • Gets the total time for the relevant period immediately when visiting an issue
    • Decreases the potential human error to near zero
    • Automatically displays the planned time of a determined time period for an issue as a Jira custom field. This allows for reporting on planned time in the Jira issue view and to include the planned time information in other Jira reports
    • Compare total estimated time with remaining planned time. Enables you to quickly query on those issues that are over- or underallocated

     

    But the use case does not limit itself to monthly planning!

    There are many other scenarios where this script can save precious time for the end user and the organization.

    For example, a manager in a consulting firm could be looking at the staff’s planned hours for a client’s issue to ensure that for a given time period, the time planned does not exceed the contractual agreement with the client. If it does, then the firm can let the client know that they will charge extra.

    Or if for example people were logging time on an off-site issue (such as meeting clients or being on the road), then it would help a manager quickly understand how much time his team is spending off-premise, and help determine the remaining capacity of his team for a predetermined time frame.

     

    How do I get my hands on the script?

     The beauty in this partnership is its simplicity. In short:

    1. Get ScriptRunner via the Atlassian Marketplace or the “Add-ons” page in Jira’ settings
    2. Head to the Tempo – Adaptavist Library found here and subscribe to the library
    3. Go to the script of interest and copy the script in your ScriptRunner
      ScriptRunner groovy script

      All you have to do is to copy-paste the script in your ScriptRunner terminal and tweak the variables to your use case.

      Are there other scripts like this?

      Today, we quickly went over one of the newly published scripts made by the Tempo-Adaptavist partnership for Tempo Planner and some scenarios in which time could be saved through automation.

      More scripts have been recently published in the Tempo-Adaptavist library. One way to learn more about those scripts would be to join the automation webinar “Save time with tempo and ScriptRunner automations” on December 5th. You can register for the event here to get a recording.

       

    Share this post

  • Color Matters

    26 December 2017
    Comments are off for this post

    Here is a post to commemorate the release of a new feature: Color Scheme Enhancement for Multiple Filters Chart Gadgets version 2.1.0

    1. “What purpose will this color serve?”
    2. “Will this (color) serve it’s purpose effectively?”

    Gif on Steps for a Custom scheme

    When color is used effectively, it brings life to the charts and directs users to focus on details required for effective communication.

    Such as to (1) highlight a particular data, (e.g. Tasks that has yet to be completed)

    (2) encode quantitative values, (e.g. Density of importance corresponds to darker shades)

    and, (3) to group items.

    Colors themselves tell a story, and it’s the responsibility of the designer to make sure the palette used does not create confusion within a data visualization.

    Thus, the palettes used are to have enough variation in hue and brightness.

    Try out the different color palettes available in Multiple Filters Chart Gadget and explore the possibilities with colors.

     

    Fun Fact:

    Image Retrieved From https://thumbnails-visually.netdna-ssl.com/color-emotion-guide_512d42458efc1_w1500.png

    Available on the Atlassian Marketplace

    Share this post

  • Get Ready For 2017 With The Right Tool

    8 December 2016
    Comments are off for this post

    “You are only as good as your tools”

    If you are using tools like IntelliJ IDEA, Resharper, PyCharm, RubyMine or WebStorm, this might be useful info for you.

    icon_IntelliJIDEAicon_resharpericon_PhpStorm icon_RubyMine icon_WebStorm

    (more…)

    Share this post

  • Powering your Dev Teams Contest #2

    8 August 2016
    Comments are off for this post

    Akeles-PowerCube-ads

    We are organising a series of contests for the IT folks in Singapore.

    For this month, 10 lucky winners with the correct answers will get to win a Allocacoc PowerCube Remote Original + PowerRemote each. 

    The submission will close on 31 August 2016 2359hrs Singapore time


    Your Name
    NRIC
    Your Email
    Phone number
    Your answer Which of the following is not true on the differences between Git and Subversion?
    Git is much faster in performance than SubversionGit doesn't need a network connection to create commitsFeature branches works better with Git branchesSubversion works on Pull Requests and Git uses branches
    Security Check captcha
    Retype the character from the picture above

      I have read and agree to the terms and conditions below

    Terms and Conditions for the contest

    1. This contest is open only to citizens and permanent residents of Singapore aged 21 and above.
    2. No purchase is required. Contestants will have to like our Facebook page
    3. Limited 1 entry person. Subsequent entries will be disqualified.
    4. Each correct entry will be limited to 1 lucky draw chance. 
    5. The winners of each lucky draw will be picked from all eligible entries.
    6. The qualifying period for this draw is 1st August 2016 – 31st August 2016.
    7. The lucky draw will be conducted electronically on 15th September 2016.
    8. Winners will be notified by 16th September 2016 via a prize notification email.
    9. Lucky Draws winner are required to respond within a week from notification date in order to be eligible winners. Winners that do not respond will be forfeited.
    10. We reserve the rights to deal with all unclaimed prizes in any manner deemed fit.
    11. Any personal information collected is for the sole purpose of conducting the Contest including the notification of the winners of the Contest. By participating in the Contest, participants consent to the Organiser’s use of their personal information in accordance with the terms and conditions of the Contest.
    12. We are not a supplier of the product(s) offered and shall not bear any liability in relation thereto.
    13. Akeles’ decision on all matters relating to the draws shall be final, binding and conclusive and no correspondence will be entertained.
    14. Participation of the Contest constitutes acceptance of the terms and conditions of the Contest.

    Share this post

  • Powering your Dev Teams Contest #1

    13 June 2016
    Comments are off for this post

    To celebrate our 8th year, we are organising a series of contests for the IT folks in Singapore.

    For the 1st month, 10 lucky winners with the correct answers will get to win a Allocacoc PowerCube Remote Original + PowerRemote each. 

    The submission will close on 30 June 2016 2359hrs Singapore time


    Your Name
    NRIC
    Your Email
    Phone number
    Your answer Which one of the following is a characteristic of Scrum projects?
    Focused on completing a deliverableAre often used by Support teams to manage a continuous flow of work itemsHave a variable-length delivery timeframeDevelopers work on issues whenever they decided to do so
    Security Check captcha
    Retype the character from the picture above

      I have read and agree to the terms and conditions below

     

    Terms and Conditions for the contest

    1. This contest is open only to citizens and permanent residents of Singapore aged 21 and above.
    2. No purchase is required. Contestants will have to like our Facebook page
    3. Limited 1 entry person. Subsequent entries will be disqualified.
    4. Each correct entry will be limited to 1 lucky draw chance. 
    5. The winners of each lucky draw will be picked from all eligible entries.
    6. The qualifying period for this draw is 1st June 2016 – 30th June 2016.
    7. The lucky draw will be conducted electronically on 15th July 2016.
    8. Winners will be notified by 16th July 2016 via a prize notification email.
    9. Lucky Draws winner are required to respond within a week from notification date in order to be eligible winners. Winners that do not respond will be forfeited.
    10. We reserve the rights to deal with all unclaimed prizes in any manner deemed fit.
    11. Any personal information collected is for the sole purpose of conducting the Contest including the notification of the winners of the Contest. By participating in the Contest, participants consent to the Organiser’s use of their personal information in accordance with the terms and conditions of the Contest.
    12. We are not a supplier of the product(s) offered and shall not bear any liability in relation thereto.
    13. Akeles’ decision on all matters relating to the draws shall be final, binding and conclusive and no correspondence will be entertained.
    14. Participation of the Contest constitutes acceptance of the terms and conditions of the Contest.

    Share this post

  • Confluence Page of the Month – CommonWealth of Massachusetts CommonWiki

    The Confluence Page of the Month for March goes to a Template & Training page from CommonWealth of Massachusetts CommonWiki

    CommonWiki

    4 reasons why we like this page

    • The content is useful
    • The template files are attached to the page and versioned automatically
    • Using composition macro to group the content in various tabs
    • Using icon to denote the type of the file

    Share this post