It has been almost 3 years since Sander Brienen wrote the post “Scaling Agile in the Enterprise with SAFe and JIRA Agile ” and had his talk at Atlassian Summit 2013. Sander’s premise to view an organisation in three levels (Portfolio, Program and Teams) and the general approach on how to plan work of his talk and blogpost are still valid. Fortunately the tooling to provide insight and overview has advanced in the past 3 years. Organisations need a new definition of success. Not the biggest organisation wins, but the organisation who gets the best fitting products to the market in the most efficient and effective way. This is a collaborative game! Continue reading
Some great new features arriving to JIRA Service Desk.
- Ease of creating linked issues
- Confluence Knowledge base articles free for customers
- Smart Graph Continue reading
Atlassian in the early years had set a goal, reach 50.000 unique clients, excluding 10 user, academic or non-profit licenses. This year they’ve actually reached it. Continue reading
Atlassian Summit is het customer facing event van Atlassian waarbij de aanwezigen als eerste te horen krijgen welke nieuwe features er aankomen, hoe klanten als Spotify de producten gebruiken en wat best practices zijn.
Bent u JIRA aan het ontdekken of heeft u het gevoel dat uw organisatie meer uit deze tool kan halen? Neem dan deel aan onze JIRA Administrator training op 21 mei! Op deze trainingsdag leren wij u alle ins en outs van JIRA, zodat u dé JIRA expert binnen uw bedrijf wordt.
As Atlassian experts we rely heavily on Atlassian products for our day to day work. Our workflow makes use of Git, Stash, Confluence, JIRA and JIRA Agile, amongst others. It so happens that the folks at Atlassian just recently released a product pack which offers you essentially the same seamless experience. It’s called Git Essentials.
JIRA is used within a great number of teams as an agile issue tracking tool. In bigger companies different scrum teams will use the same tool to manage the company backlog. Program or project management often set up a corporate backlog of issues from which tasks are distributed across the different teams.
But teams are not an entity in Jira. So how should you go about distributing tasks between your different teams in JIRA? This post describes several solutions to that problem that we use ourselves and have seen in the field.
That said, we are very much interested in your solutions, so let us know what they are in the comments below!
Read on to find out how combining JIRA Service Desk and Confluence Team Calendars makes requesting time off easier than ever…