Onboarding Agile and Atlassian with E7

  

We recently broke down how we observe a client’s environment and structure before developing and implementing a plan that best suits that specific client. We decided to now take it a step further into what that transformation and implementation looks like.

From customization to strategic planning, there are many factors in between. Training teams in maximizing the benefits of Atlassian methodology and the tools at hand and learning how they align with one another are a few examples of how that plan plays out, such as Jira’s ticket structure or Confluence’s adaptation to everyday project procedures.

Click on the video above to hear how Ana Galofre and Michael Abdelnour explain what happens after the discovery process. Or skim through the transcription below.

Video Transcription

Michael: 00:01

Hey Ana. Good afternoon, how are you?

Ana: 00:02

Hey, Mike, I'm doing well. How are you?

Michael: 00:05

Doing good. I thought this week we would flip the script a little bit and maybe I can ask you a question or two.

Ana: 00:11

I love it, yeah, what do you have?

Michael: 00:15

Awesome. So up until now, we've talked a lot about the tools, the features, the differences in the platform between cloud and server and premium, and all these platform based ideas. But talk to me a little bit about what we do in terms of transformation and in terms of rolling these tools out, and what makes that process unique within the Atlassian ecosystem?

Ana: 00:40

Okay. Yeah, I would love to. So we have talked a little bit about our discovery process, how we go in and analyze a client environment. But I would say from there, as far as implementation, it's really a two-prong methodology that we take on for digital transformation. So one is, of course, customizing the tools to a client's particular environment, and not just IT, but we're seeing more and more implementation across the board and strategic planning and marketing and human resources, all of the applications across the org, which is great.

But the change management also really entails a lot of training on process, so going in and introducing scrum methodology, what are the different roles, what's a scrum master, what are ceremonies, what are daily... ups? How do you use the tools in that daily team management and team cadence to get the most out of the whole stack?

So mainly I would say Jira is used for creating the tickets, moving those tickets through workflows on the board. And then Confluence has really stepped up its game, especially in cloud, having tons of out of the box templates for helping run the day-to-day of those projects, whether it be a decision matrix or the initial ones that they have always had with meeting notes and product requirements and that type of thing.

But now there's a whole out of the box ecosystem that you can employ with templates to run that day-to-day project. So that handshake is really important, but that combination of training on process and what is agile and what are the different roles that the team has to take on for that, and then how do they overlay with the tools, because either the training alone or the tools alone doesn't really get the job done.

Michael: 02:36

Yeah. It really encompasses the word transformation. When folks are going from maybe the way they've been working for years or however they're working today, into more of a fluid and agile fashion, it's not just the tools, it's all those things that you talked about. And so being able to provide that training and handholding and configuring the tools to allow them to be successful is really all encompassed.

Ana: 03:02

It is. Yeah.

Michael: 03:05

Yeah. How would you say the Atlassian cloud today positions that for an advantage, as opposed to maybe a traditional mindset?

Ana: 03:19

I think that the integration between all of the different tools within the Atlassian stack really makes for a seamless experience. So you don't just have this one silo of, "Okay, here are my tickets that I'm working through, and then I have stuff in five other applications." The integration aspect is huge, so you can really track all of your business teams and your product teams can do all their work in Confluence, and then just do a really easy link out to the Jira ticket and see that status. That's huge.

And again, I think the learning that Atlassian has listened to how, over the years, how are all of these teams customizing the experience, and then trying to provide that out of the box so that we can really employ best practices as quickly as possible with all of their set templates and those things, and really just hitting the ground running.

Michael: 04:23

Yeah. No, that's great insight. I appreciate it, Ana. I know a lot of folks when they call and they're asking about the tools or the platform, it's usually a bigger discussion than that. It's not just about the tool, it's usually about what are they trying to accomplish in terms of how they're working and how they're tracking their work. And I appreciate your time, that was a great insight.

Ana: 04:47

Yeah, anytime, talk soon.

Michael: 04:50

All right. Take care.

Ana: 04:50

Bye.

Migrate to the Cloud

Subscribe to Our Resources

For weekly news and tech tips.