Watch this video for a quick introduction to StatusPage, how it can help you communicate with your users during downtime, and learn how to get started. To create your trial today, head over to https://atlassian.com/statuspage
5 год назад
An 8 minute video on how a world-leading equipment manufacturer drastically reduced costs and improved service by using the Tosibox solution to solve remote connectivity problems with their globally connected fleet of wash systems
9 мес назад
Atlassian Mountain View is our newest hub for mobile and cloud development. One of the teams tackling this head on is Confluence Cloud. The team is evolving to prepare for scalability and reliability in the cloud and is looking to grow. Listen to what some of our engineers are creating and find out how you can help redefine Confluence's future. Check out our open roles in Mountain View on the team here: https://www.atlassian.com/company/careers/mountain-view
1 год назад
https://www.programmableweb.com/api-university/what-are-apis-and-how-do-they-work - This series is for those who want to learn more about APIs (Application Programming Interfaces). Maybe you read about them on Fortune magazine or somewhere else on the net. You want to get smart and to be able to have a conversation. We’re going to deliver to you today, a basic to intermediate understanding "What is an API", and how they’re important. What sort of benefits you can get if you start to put them to use in your organization. In the first part of our API 101 video series, we build on concepts such as an API being a User Interface (UI) that is different from the UIs that we are used to such as the User Interface on a smart phone. We all know what to do with them. We can see them, use them, touch them, and we all have an expectation of how it’s supposed to work. Machines need their own interfaces, they don’t have brains, fingers or eyes. They need their own understanding of how to talk to each other. That understanding is what we call a contract.
2 год назад
Nicola Paolucci Developer Advocate, Atlassian When you adopted Git you either researched an effective workflow or someone in your team chose it for you. Maybe you use Gitflow, maybe a lightweight master/develop system like the Bitbucket Cloud team, or maybe you have long-running maintenance branches. Done right, all these workflows can be very effective for your team. But why is the Git project itself run by e-mailing patches to an old school mailing list? Why do you hear of cool companies like Twitter use huge mono repos and embracing patch queues? To answer these questions we need to go deeper. This talk will show you the cool side of Git workflows you are probably not using.
1 год назад
This is the tale of two Agile teams. It wasn't just an organisational separation: it was an AGILE separation. Download your FREE CHEAT SHEET: http://bit.ly/scrum-vs-kanban-cheatsheet This is a story of Two Agile Teams. More correctly, it’s the tale of one Agile Team that split into two Agile Teams. What makes the story interesting is that it was more than just an organisational separation. It was an Agile separation: - One team continued as before - with *Scrum* - The other team dropped Scrum in favour of *Kanban* Will it all end in tears? → SUBSCRIBE for a NEW EPISODE every WEDNESDAY: http://www.DevelopmentThatPays.com/-/subscribe ------------------- 100. Scrum vs Kanban - Two Agile Teams Go Head-to-Head + FREE CHEAT SHEET This is a Tale of Two Agile Teams. More correctly, it’s the tale of one Agile Team that split into two Agile Teams. It was more than an organisational separation. It was an Agile separation. Act One It was 2012 when I first walked into the offices of the BBC. The same time and the building as these guys… Never saw them. Which is strange. The software team I joined was one, I was told, that 'did Agile'. At the time, I knew very little about 'Agile'. But I could see from the get go that they weren’t doing it by halves. There’d clearly been lots of training. They had all kinds of tools. They were doing all kinds of 'rituals'. We’ll get into the specifics of how the team worked in a minute. The Split ----- Fast forward a year and the department reorganised. My team was split in two. Although reporting lines changed, the seating plan didn’t. There was one outward indication of change: where there had been one agile board, there were now two. Oh, and we did two stand-ups every day: ours at 10:00am, theirs at 10:15. A New Flavour ------- Ever-observant, it took me a couple of weeks to notice that the other team was doing a different 'flavour' of Agile. I hadn’t realised that there was more than one flavour of Agile! What my team was doing was, called Scrum. The other team was doing something called Kanban. Kanban Really This was a word I knew from way back. But I knew it in the context of manufacturing. I couldn’t immediately see how it applied to the process used by my (former) teammates. So I went to talk to the Lead Developer of 'Team Kanban'. 'What the difference between Scrum and Kanban ' I asked He was ready with an immediate answer: 'You Guys Talk About Work. We Do Work.' Ouch! in that moment, I learned an important lesson about Agile: it can be an emotive issue. Beliefs can be deep-seated. The Team Kanban Lead Dev clearly thought that Kanban was better than Scrum. I held… the opposite view. My view was both strongly held… and completely without evidential foundation. Natural Experiment ---- I’m a little older now. And, I hope, a little wiser. I can now see that the team split was a perfect Natural Experiment. You know the kind of thing: “Take two identical twins. Separate them at birth. Feed one Scrum. Feed the other Kanban. Observe the result.” So I hope you’ll join me on a little forensic investigation, starting with a 20,000 view of each team's processes. Team Scrum ----- My team - let’s call it "Team Scrum" - worked in two-week Sprints. At the beginning of s Sprint, we’d take ourselves off to a quiet part of the building for a Sprint Planning session. The Product Owner would select items from the backlog, and we’d play “Planning Poker” to estimate the size each item. We’d continue until we had roughly one “Sprint’s worth” of cards. Sprint Planning over, each developer would pick up a card and set to work Every morning there’d be a Stand-up - aka a Daily Scrum - 10 am on the dot. And so it would go on day after day, with the cards gradually making their way across the board. By the about the Tuesday of the second week, we’d expect all of the cards to have moved at least one step. It was then a race - a "sprint" - to get everything tested and ready for release on Friday. We didn’t always succeed in getting everything across the board: any item that failed to make it would be “recycled” into the next Sprint. On the Friday morning, everything in the release column would be packaged for release. Oh, and one last thing to round out the Sprint: a Retrospective: a chance for the team to get together to reflect on what well, to discuss what could be improved, and to commit to one or two action items for the following Sprint. Taking stock of the evidence: There’s a Product Backlog, the Agile Board, and a Done Pile. There’s a two-week Sprint with a Sprint Planning session at the beginning. Each day after that, a Daily Scrum Meeting - aka a Daily Stand-up. At the end of the process, all those cards that https://www.youtube.com/watch?v=HNd1_irOL5k
3 мес назад
Learn more at: www.atlassian.com/ops Jira Ops is a central hub for teams to more efficiently respond, resolve and learn from every incident. It brings together the most important aspects of modern incident management, including alerting, team chat, customer communications, and documentation. Jira Ops includes the following for software and IT teams: Alerting - easily provide first responders the ability to raise a Jira Ops incident directly from the alert. Incident chat - automatically spin-up an associated Slack channel directly from the Jira Ops incident and take action by sending key messages to the Jira Ops timeline. Statuspage comms - keep your customers in the loop during downtime directly from an incident in Jira Ops. Incident timeline - quickly get key stakeholders up to speed on the incident without slowing the team down. Key events like alerting updates, important chat messages in Slack, and Statuspage announcements are automatically pulled into the timeline. Postmortems - learn and improve after every incident by pulling key timeline info into a postmortem document that's linked to your Jira Ops incident. Atlassian incident management handbook - steal our secret sauce and gain access to our best practices and our approach to modern incident management. See how it works: www.atlassian.com/ops
2 год назад
Learn what Docker is, what it isn’t, and why it’s useful to you as a coder. Suggested Resources: https://coderjourney.com/resources Twitter: https://twitter.com/coderjourney Intro created by Ian Zainea (http://ianzainea.com) -~-~~-~~~-~~-~- Please watch: "How to Write Better Automated Tests" https://www.youtube.com/watch?v=BDu6oyfKPfg -~-~~-~~~-~~-~-
3 год назад
A PM and a developer walk into a bar... That's a joke all on it's own! Creating a team dynamic where engineering and product management compliment each other can feel like a pipe dream. Confluence's Sherif Mansour (Principal Product Manager) will share and explore the familiar anti-patterns faced when product and engineering collaborate. Come for the practical tips about how to improve your team's most important relationship.