Business Consultants or Atlassian Consultants

Ravi Sagar
3 Jul 202215:53

Summary

TLDRIn this video, the speaker discusses the distinction between being a business consultant and an Atlassian consultant, emphasizing the need to choose a specialization. They highlight the importance of understanding the technical aspects of tools like Jira for Atlassian consultants and the process-oriented focus for business consultants. The speaker also touches on the value consultants bring to organizations through their experience and the significance of tool setup for efficient delivery and collaboration in agile environments like Scrum or Kanban.

Takeaways

  • 🔧 The speaker discusses the distinction between being a business consultant and an Atlassian consultant, emphasizing the need to decide whether to focus on the technical or business aspects of consulting.
  • 🛠️ Atlassian consultants are expected to have in-depth knowledge of the tools they work with, such as Jira, and should be able to add value by setting up and troubleshooting the tool for clients.
  • 💼 Business consultants, on the other hand, may not need to be experts in the tool itself but should have a solid understanding of business processes and methodologies like Scrum or Kanban.
  • 📈 The speaker highlights the importance of delivery and efficiency when using tools like Jira, stating that the primary goal should be to facilitate on-time delivery and cost savings.
  • 👥 Collaboration and remote work are key aspects that tools like Jira aim to improve, making it easier for teams to find information and work together effectively.
  • 💬 There is an overlap between the roles of business consultants and Atlassian consultants, as both may need to understand the business side and the technical aspects of using tools like Jira.
  • 💼 The speaker suggests that business consultants should focus on the process and methodology, letting the technical consultants handle the tool-specific intricacies.
  • 💼 Scrum masters or business consultants are expected to coach teams on how to work in an agile or iterative fashion, rather than getting too involved in the technical aspects of the tool.
  • 🛠️ Atlassian consultants are often the highest-paid roles because they bring experience and add significant value to organizations by ensuring the tool works perfectly for their needs.
  • 🔍 Jira's flexibility allows teams to customize their workflows, such as using story points or t-shirt sizes for estimation, and consultants can help tailor the tool to fit these needs.

Q & A

  • What is the main focus of the video script?

    -The main focus of the video script is to discuss the roles and responsibilities of Atlassian consultants, particularly the distinction between a business consultant and an Atlassian technical consultant, and the importance of choosing a clear career path in these areas.

  • Why should one not be a business consultant along with being an Atlassian consultant?

    -The speaker suggests that one should not be a business consultant along with being an Atlassian consultant because the roles require different skill sets and focus areas. A clear decision should be made to specialize either on the technical aspects of the tools or on the business processes and methodologies.

  • What is the value that Atlassian consultants bring to an organization?

    -Atlassian consultants bring value to an organization by leveraging their experience with the tools, helping to set up and optimize the tools for the organization's specific needs, ensuring smooth collaboration, and contributing to efficient and timely delivery of projects.

  • What is the difference between releasing and deploying in the context of product development?

    -Releasing refers to making a feature ready to go live, while deploying is the actual act of going live with the feature. The speaker emphasizes the importance of the team's ability to deliver and the role of tools like Jira in facilitating this process.

  • How does the speaker describe the role of a business consultant in the context of Agile methodologies?

    -The speaker describes the role of a business consultant as someone who understands and can coach teams on Agile methodologies like Scrum or Kanban. They are expected to have some knowledge of the tools but should primarily focus on the business processes and team dynamics.

  • What is the importance of visibility in the context of using tools like Jira?

    -Visibility is important because it allows managers, Scrum masters, and leads to monitor and understand how teams are working, track the progress of tasks, and ensure that the tools are being used effectively to support the team's workflow.

  • What is the speaker's view on the overlap between the roles of a business consultant and an Atlassian consultant?

    -The speaker acknowledges that there is an overlap between the roles, as both need to understand certain aspects of the business processes and the tools. However, the main difference lies in the focus area, with Atlassian consultants being more on the technical side and business consultants on the process side.

  • Why are Atlassian consultants considered to be highly paid compared to engineers or developers?

    -Atlassian consultants are considered to be highly paid because they bring valuable experience and expertise to an organization. Their role is to add value by optimizing the use of Atlassian tools, which can lead to increased efficiency and better project outcomes.

  • What is the speaker's advice for someone considering a career as a consultant?

    -The speaker advises that one should decide whether they want to focus on the technical side or the business side of consulting. They should understand the specific demands of each role and choose the path that aligns with their skills and interests.

  • How can Jira be customized to support different Agile methodologies?

    -Jira can be customized by creating additional fields to capture different types of estimations like story points or t-shirt sizes, and by setting up automation rules or scripts to support the specific practices of the chosen Agile methodology.

  • What is the role of a Scrum master in a team following Agile methodologies?

    -The Scrum master's role is to facilitate the team's adherence to Agile principles and practices, help them work in an iterative sprint mode, and ensure that the team's workflow is efficient and effective. They should also address issues like team member idleness and promote collaboration within the team.

Outlines

00:00

🔧 The Role of a Technical Consultant in Atlassian Tools

The speaker discusses the importance of specialization when choosing a career path in Atlassian tools. They emphasize that one should decide whether to become a business consultant or an Atlassian consultant, focusing on either the technical or business aspects of tool utilization. The value that Atlassian consultants bring to an organization is highlighted, including their expertise in setting up and optimizing tools like Jira for efficient collaboration and delivery. The speaker also touches on the necessity for consultants to be well-compensated for their experience and the value they add.

05:01

🛠 Distinguishing Between Business and Technical Consultancy in Agile Practices

This paragraph delves into the differences between business consultants and Atlassian consultants, particularly in the context of agile methodologies like Scrum. The speaker explains that while business consultants, such as Scrum Masters, focus on coaching teams to adopt agile processes, Atlassian consultants are responsible for ensuring the technical tools support these processes effectively. The importance of understanding and integrating tools to meet specific business needs is underscored, as well as the consultants' role in adding value through customization and automation.

10:02

📊 Balancing Technical Expertise with Business Acumen in Consultancy

The speaker continues to explore the distinction between business and technical consultants, stressing that while there is an overlap in knowledge, their core competencies differ. Business consultants should have a broad understanding of various tools but primarily focus on team dynamics and process improvements. In contrast, Atlassian consultants should have a deep technical understanding to customize and integrate tools to fit the clients' needs. The speaker also discusses the importance of tracking work and identifying team members' contributions using tools like Jira to ensure productivity and continuous delivery.

15:02

🤔 Choosing a Path in Consultancy: Business or Technical Focus?

In the final paragraph, the speaker wraps up the discussion by encouraging individuals to consider their interests and strengths when deciding to become a consultant. They highlight the importance of choosing between a business or technical focus and understanding the implications of that choice for their career. The speaker invites viewers to ask questions and reach out for further discussion on career options in the Atlassian field, offering their website as a point of contact for additional support.

Mindmap

Keywords

💡Atlassian Tools

Atlassian Tools refer to a suite of software solutions designed to improve productivity and collaboration within a team or organization. In the script, the speaker discusses their focus on Atlassian's Jira, a popular project management tool, and emphasizes the importance of understanding these tools for both business and technical consultants.

💡Jira

Jira is a project management software developed by Atlassian, which is widely used for bug tracking, issue tracking, and project management. The script mentions Jira multiple times, highlighting its role in facilitating collaboration, remote work, and efficient delivery of products or services.

💡Consultant

A consultant is a professional who provides expert advice in a particular area. The video script discusses the distinction between a business consultant and an Atlassian consultant, emphasizing the need for consultants to specialize in either the technical or business aspects of tool utilization.

💡Business Consultant

A business consultant specializes in advising organizations on matters such as strategy, operations, and processes to improve efficiency and performance. In the script, the speaker suggests that a business consultant should focus on the non-technical side, such as coaching teams in agile methodologies like Scrum.

💡Atlassian Consultant

An Atlassian consultant is an expert in Atlassian's suite of tools, providing technical guidance on their setup, integration, and optimization. The script differentiates this role from a business consultant, noting that Atlassian consultants should have in-depth knowledge of the tools' functionalities.

💡Agile

Agile is a methodology for project management and product development that emphasizes flexibility, collaboration, and rapid, iterative progress. The script mentions agile in the context of using Jira to support agile practices like Scrum and Kanban.

💡Scrum

Scrum is a framework within the Agile methodology that structures development into iterative cycles called sprints. The speaker in the script discusses the role of a Scrum master and how Jira can be used to facilitate Scrum practices.

💡Delivery

In the context of the script, delivery refers to the process of releasing a product or service to the end-user. The speaker stresses that the primary goal of using tools like Jira is to ensure timely and efficient delivery, which is critical for business success.

💡Integration

Integration in the script refers to the process of linking different tools and systems together to work seamlessly. The speaker mentions the need for Atlassian consultants to ensure that tools are well-integrated, which can involve automation and scripting.

💡Automation

Automation is the use of technology to perform tasks without human intervention. The script discusses how Atlassian consultants might use automation to streamline processes within Jira, such as setting up notifications or scheduled jobs.

💡Estimation

Estimation in project management is the process of predicting the effort, time, or resources needed to complete a task or project. The script mentions different estimation techniques like story points and t-shirt sizes, which can be used in Jira to help teams plan their work.

Highlights

Discussion on the role of a business consultant in the context of Atlassian tools, emphasizing the importance of specialization.

The necessity for Atlassian consultants to have a deep understanding of Jira and its capabilities.

Consultants are expected to bring value by leveraging their experience with tools like Jira.

The high earning potential for consultants due to their expertise and the value they add.

The importance of tool setup for efficient collaboration and timely delivery in organizations.

The critical role of delivery in the success of using tools like Jira in a business context.

The difference between releasing and deploying in product development cycles.

The example of fintech mobile apps and the importance of continuous delivery and app reliability.

The overlap and distinction between the roles of business consultants and Atlassian consultants.

The expectation for business consultants to have knowledge of tools but focus on process and team dynamics.

The technical consultant's role in ensuring tools like Jira work flawlessly for a company's specific needs.

The flexibility of Jira to adapt to different methodologies like Scrum, Kanban, and others.

The potential for Jira to track work and monitor team member activity through commit messages and issue keys.

The challenge of managing team members' workload and ensuring even distribution of tasks in Scrum teams.

The importance of visibility provided by tools like Jira for managers and Scrum masters to make informed decisions.

Advice for those considering a career as a consultant to decide whether to focus on the technical or business side.

Invitation for viewers to ask questions about career options in the Atlassian field and offer of support via the website.

Transcripts

play00:11

hello everyone so

play00:13

these days i'm talking quite a lot about

play00:16

things i mean in general carrier

play00:20

in atlassian tools and of course my

play00:23

channel is all about you know classroom

play00:24

tools jira

play00:26

and of course most of the times 99

play00:28

percent of the times i actually show you

play00:30

things in the tool but i think

play00:32

i have so many videos i have covered

play00:35

quite a lot when it comes to

play00:38

doing things in the tool i think i think

play00:41

from time to time i also like to share

play00:44

with you

play00:45

or talk about

play00:47

you know

play00:49

carrier options in atlassian tools and

play00:52

also especially when it comes to

play00:56

choosing

play00:57

your path when it comes to

play01:00

atlassian then i think i have

play01:03

quite a lot to share so in this video i

play01:06

actually wanted to talk about

play01:08

business consultant now

play01:12

think and of course now you might

play01:13

disagree with me but you know we all

play01:15

have our we have we all have our

play01:16

opinions i think

play01:18

uh you should not be a business

play01:20

consultant

play01:21

uh

play01:23

along with the ajira consultant or or an

play01:25

atlassian consultant you have to

play01:27

basically decide whether you want to be

play01:29

a business consultant and

play01:32

you

play01:33

have to also decide whether you want to

play01:35

focus on the technical aspects of it i

play01:37

think when it comes to classroom

play01:38

consultation

play01:40

and i'm being serious when it comes to

play01:41

attaching consultations uh atlassian

play01:43

consultants are supposed to be

play01:47

uh i'm talking about the value that they

play01:49

bring when you hire a when you hire and

play01:51

consult when you hire an atlassian

play01:53

consultant

play01:54

they're supposed to

play01:55

work

play01:56

or they're supposed to know how tool

play01:58

works and uh when it comes to a tool

play02:02

like jira

play02:04

uh there is no end to it right

play02:05

if you're a consultant you can't really

play02:07

say that say to your client that okay i

play02:09

know about you know these things but

play02:10

maybe you know not everything else which

play02:12

is okay i'm not really saying that you

play02:13

should know each and everything but uh

play02:15

if you're a consultant you're probably

play02:17

experienced

play02:18

i mean that is why you are a consultant

play02:19

that is why they have paid you money for

play02:22

example consultants are usually the

play02:24

highest

play02:25

paid i mean i'm not really sure about

play02:28

other levels i'm i mean maybe ceos ceos

play02:30

are paid more for sure but our top

play02:33

managerial positions but consultants are

play02:35

definitely you know paid quite a lot as

play02:38

compared to you know engineers or

play02:40

developers because consultants

play02:43

bring

play02:44

their experience they add value to

play02:47

what the organization is trying to

play02:49

achieve with these tools and people when

play02:52

they use a tool like in fact any tool

play02:54

but if you talk about jira

play02:56

uh

play02:57

the whole idea of using a tool like jira

play02:59

or confluence or you know github

play03:02

or any other tool the whole idea is to

play03:04

collaborate is to work remotely is to

play03:07

make sure that people are able to find

play03:09

their stuff easily and

play03:12

the outcome is that you're able to

play03:13

deliver on time you're saving money

play03:15

you're working efficiently and if you

play03:18

set up your tools correctly if you

play03:20

ensure that your tools are not stopping

play03:22

you not causing any problems when it

play03:24

comes to delivering i think delivery

play03:26

should always be the top most priority

play03:28

if you're not delivering then

play03:31

tools are of no use and when it comes to

play03:34

business consultation i think

play03:36

if let us let us let me give you a very

play03:38

simple example let us say there is a

play03:40

company trying to

play03:42

develop

play03:44

a product right and or maybe they

play03:46

already have a product and they want to

play03:48

launch

play03:49

uh or leave something every

play03:52

every other

play03:53

week or maybe every year every other

play03:55

month right let us say every other month

play03:57

or maybe they are delivering every two

play03:59

weeks so they are constantly

play04:01

uh doing

play04:03

things they are releasing things they

play04:04

are deploying things and when it comes

play04:06

to releasing i think releasing and

play04:07

deploying is totally different when you

play04:09

release something that you have

play04:11

when you release something so you have a

play04:12

feature which is ready to go live

play04:14

but deploying is actually going live

play04:16

right now uh what i'm trying to say is

play04:18

that you are working in this environment

play04:20

where uh

play04:22

teams need to constantly you know

play04:24

deliver right because that is the demand

play04:27

of the industry for example if you're

play04:28

working on fintech uh you know these

play04:30

days we have a lot of those mobile apps

play04:32

where uh

play04:34

there are so many apps like there are so

play04:36

many like in the uk we have monzo we

play04:38

have revolut we have

play04:39

counting up we have so many small or

play04:42

tied whatever there are so many mobile

play04:44

based banking apps uh like proper bag

play04:47

bank

play04:48

which is of course online on your mobile

play04:50

app there is not even a website i mean

play04:52

they do have a website but all the

play04:53

banking is done using mobile app so that

play04:55

mobile app

play04:56

is basically

play04:57

your business it is your retail right so

play04:59

you need to always make sure that your

play05:01

apps are working perfectly fine

play05:03

uh you might not be adding a lot of new

play05:05

features but

play05:07

with the new

play05:09

android versions different devices your

play05:11

app should should basically

play05:14

work flawlessly i mean if i'm if let's

play05:16

say i'm trying to make a payment or if

play05:18

i'm trying to maybe check my balance i

play05:20

should be able to write so

play05:22

it is a bit critical right because

play05:23

you're dealing with people's money and

play05:26

uh this is of course a very competitive

play05:28

industry so this team i'm going back to

play05:30

the team this team is of course supposed

play05:32

to

play05:33

work

play05:34

uh

play05:35

easily together

play05:36

and let us say they are

play05:38

using jira you know in a very simple way

play05:40

they are just using jira where or they

play05:42

want to use hero let us say they want to

play05:43

use shira or maybe they are already

play05:44

using jira but they want to improve few

play05:46

things and they follow or they try to

play05:47

follow scrum or agile and maybe

play05:50

they they're not entirely sure whether

play05:52

they should use story points or

play05:55

or maybe they should use a t-shirt size

play05:58

or you know some kind of estimation to

play05:59

estimate the work

play06:01

and maybe they need a bit of help with

play06:04

how to create uh

play06:06

a story or a backlog so i think this is

play06:09

probably more on the business side where

play06:11

you have let us say

play06:13

uh you're gonna probably hire a

play06:15

consultant and when i say business

play06:17

consultant i'm talking about scrum

play06:19

master someone who has been doing these

play06:21

things and someone who can probably come

play06:23

and coach these teams to maybe you know

play06:27

uh use the use of course or basically

play06:29

adopt these processes answer this their

play06:31

questions on the on the business side of

play06:33

things like on the on the process side

play06:35

uh but of course they are also expected

play06:37

to have some knowledge of the tool but

play06:40

they are not supposed to be

play06:42

like

play06:43

the tool guy right now that is where

play06:45

there is a difference we as an

play06:47

attraction consultants we know really

play06:50

well how tools how these tools like jira

play06:53

conference big bucket work

play06:55

we can

play06:56

set up their pipeline we can we can make

play06:59

sure that whenever something happens in

play07:01

the tool uh they get notification so

play07:04

in this particular case they might be

play07:05

using jita in in the most simplest way

play07:08

but maybe they have other tools and they

play07:10

need to make sure that things talk to

play07:11

each other

play07:12

and

play07:13

tools should work flawlessly so because

play07:15

they rely on the tool and of course you

play07:17

might need to do some integration you

play07:18

might need to do some automation you

play07:20

might need to you know write a script

play07:21

for them or some scheduled jobs for them

play07:24

to send them a daily reminder because

play07:26

every company is different although jira

play07:28

has a lot of standard features there are

play07:29

a lot of apps but i think

play07:32

when you really want to

play07:33

uh because gita can do probably 80 of

play07:35

the things the remaining 20 or 19

play07:38

percent is probably

play07:39

uh

play07:40

can be achieved with the help of those

play07:42

apps right but the remaining one person

play07:44

is where you will

play07:46

basically add value and you will

play07:47

basically you know finish everything and

play07:49

you will

play07:50

basically make the tool work for them

play07:52

and that is where you know the the value

play07:55

will be added by you as a consultant as

play07:57

a technical consultant because you will

play07:59

basically make sure that the tool works

play08:01

perfectly for them the way they want and

play08:03

of course you can tell them okay this

play08:04

will not work this will work from tools

play08:06

perspective and of course when it comes

play08:07

to you know tool like jeera for example

play08:10

if i work with those scrub masters i can

play08:12

tell them that yeah i know about uh you

play08:14

know story points but i don't really you

play08:16

know uh always

play08:19

dictate or help them on the business

play08:22

side of things i let them do their

play08:23

things i i of course you know let them

play08:25

uh

play08:28

work on their process and i of course

play08:31

i'm usually part of their way of working

play08:33

when they are trying to adopt a new

play08:35

methodology for example maybe some teams

play08:37

want to adopt kanban because my

play08:39

responsibility is to make sure that jira

play08:41

works for them and at the same time i

play08:43

can straightaway tell them from the very

play08:44

beginning when they are trying feminine

play08:45

when they're having those discussions

play08:47

along with the business consultant that

play08:49

yes

play08:50

uh

play08:50

jira can do that or maybe not but maybe

play08:53

there is a workaround or maybe don't do

play08:55

it at all but

play08:57

atlassian consultants are different from

play08:58

business consultants there is slightly

play09:02

there is an overlap there there is

play09:04

definitely you know

play09:05

because

play09:06

there are a lot of things that you need

play09:07

to know about those things on the

play09:08

business side

play09:09

uh and that business consultant need to

play09:11

know about how tools how these tools

play09:14

work but i think

play09:15

apart from that overlap

play09:17

when it comes to that remaining one

play09:19

person where you will basically bring

play09:20

value because you're at your business

play09:22

consultant your scrum masters might not

play09:24

know how to write a script right they

play09:26

might not even know how to use a smart

play09:28

value they might be able to create those

play09:30

simple automation rules but i i don't

play09:32

really think they should probably worry

play09:34

about the tool in fact they need not

play09:36

even look at the tools they shouldn't

play09:37

they should probably focus on

play09:39

how the teams should work uh

play09:42

like

play09:43

in

play09:44

scrum or kanban fashion or whatever

play09:46

methodology that they want to follow and

play09:48

also at the say at the same time good

play09:50

thing about jira is at jira if you talk

play09:53

about jira software

play09:55

if you want to follow agile you can but

play09:57

jira will not really enforce you or

play10:00

i'm talking about out of the box

play10:01

settings the jira software features you

play10:03

know the backlog and the sprints and the

play10:05

ranking i think it is really uh i mean

play10:09

it is in a way

play10:11

very similar to what uh scrum teams want

play10:14

to do but at the same time it is not

play10:16

very it is not very restrictive there

play10:19

are some flexibilities for example i did

play10:20

make i think i made a video recently

play10:22

where i mentioned

play10:23

uh you need not to use story points you

play10:25

can always use

play10:26

something like

play10:28

numbers right which is like estimation

play10:30

based on

play10:31

your original time estimates good thing

play10:33

about jira is that you can always create

play10:35

some fields to you know capture those

play10:36

you know other additional things like

play10:39

t-shirt size for example and there are a

play10:40

lot of ways of doing it by the way and

play10:42

we all know about poker planning you can

play10:44

also do poker planning there is also an

play10:47

app for that in a couple of apps along

play10:49

with mobile apps but talking about the

play10:51

skill sets talking about i mean this

play10:53

video is focused on business consultant

play10:55

versus

play10:56

atlassian consultant attraction

play10:58

consultants uh although there is an

play11:00

overlap but attraction consultant is on

play11:02

the technical side of things business

play11:04

consultant is on the business side of

play11:06

things and

play11:07

when you're trying to hire someone or

play11:09

maybe when you're trying to

play11:11

decide whether you want to be a business

play11:12

consultant if you want to be a business

play11:14

consultant great but don't worry too

play11:17

much about the tool in fact you should

play11:18

know

play11:20

about maybe multiple tools you know a

play11:21

bit of everything but even if you don't

play11:23

know about jira or rally or any other

play11:26

those

play11:27

uh tools that will let teams work

play11:30

using using scrum it is totally okay you

play11:32

just need to tell them what scrum is you

play11:34

just need to make sure that make sure

play11:35

that teams know how to uh work in a

play11:39

uh iterative

play11:41

uh sprint

play11:42

mode and not many people are actually

play11:45

able to do it to be honest when it comes

play11:47

to agile um it is a bit

play11:50

difficult for teams because uh

play11:53

the whole idea of a scrum is i mean i

play11:55

know quite a lot i'm not a dsc master by

play11:56

the way but i know a lot about it

play11:58

because

play11:59

i've worked with people i've worked with

play12:00

teams in the past so when it comes to

play12:02

let's say

play12:04

those sprints the whole idea is that you

play12:06

have a team let us say of three people

play12:07

or four people or five people you give

play12:09

them the start these responsibilities or

play12:11

you know these stories that they decide

play12:13

that okay i can deliver in the next two

play12:16

or not day but maybe the product owner

play12:18

the longest commaster

play12:20

when they agree agree it's the right

play12:21

word when they agree okay we can deliver

play12:23

this in the next two weeks then they

play12:25

should focus on that and

play12:27

uh sometimes i mean not sometimes quite

play12:30

regularly when these teams work

play12:33

in this iterative session sometimes

play12:35

they're able to deliver

play12:37

everything sometimes they're not even

play12:38

really able to deliver everything uh

play12:40

usually

play12:41

if you talk about let us say team

play12:42

members it happens quite a lot by the

play12:44

way uh let us say you have a team of

play12:46

five in your scrum team two of them are

play12:48

really good and they basically do their

play12:50

work in two or three days and then and

play12:51

the remaining time they are a bit idle

play12:54

which is a bit of a problem because they

play12:55

have delivered because you know they

play12:57

have delivered what they agreed to but

play12:59

at the same time

play13:00

they are of course idle uh which is

play13:03

probably

play13:04

not okay for a long time i mean it is

play13:06

okay to be ideal for like you know

play13:08

uh sometime maybe you know during the

play13:10

day if you are maybe able to deliver for

play13:12

maybe if you're if you're able to

play13:14

deliver what you agree to deliver in in

play13:16

maybe three hours four hours then of

play13:18

course it is fine you can of course

play13:19

enjoy your remaining time learn

play13:21

something but as a manager as a scrum

play13:22

master you need to identify these things

play13:25

that you know some of the team members

play13:26

are really good so maybe promote them

play13:28

maybe make them responsible for

play13:31

uh helping others and tools like jira

play13:34

can definitely

play13:35

help

play13:37

with these things you can actually

play13:38

identify for example you can build a

play13:40

report to identify okay the time that

play13:42

people are logging you can also identify

play13:44

uh for example if you have like a very

play13:45

good system where

play13:46

let us say you're writing code right

play13:48

your team is writing code so let them

play13:50

write code but make sure that the commit

play13:52

messages should have issue key so the

play13:55

moment they have issue keys i mean if

play13:56

they're committing their code

play13:58

then

play13:59

or maybe make make it a habit or not not

play14:01

really have it but there should be this

play14:03

culture where they should probably co

play14:05

commit their code regularly so whenever

play14:07

they commit their code uh you can check

play14:09

for the keys and whenever there is a key

play14:12

in bitbucket there is a possibility to

play14:13

basically make sure that there are some

play14:15

pre-commit hooks so that uh

play14:18

each command should have a key and

play14:20

when you have a key then of course you

play14:22

can track the work

play14:24

and

play14:25

you can also track whether people are

play14:27

logging time or not if not

play14:29

then of course you can probably chase

play14:30

them or maybe you can monitor or you can

play14:32

probably just understand to understand

play14:34

how teams are working i mean the whole

play14:35

idea about these tools is that these

play14:37

tools will

play14:38

give you

play14:39

uh this visibility of what is happening

play14:42

but end of the day it is for you as a

play14:45

manager as a scrum master as a lead to

play14:48

make it work for you but of course i

play14:50

think i'm probably you know just

play14:53

talking about i think i'm not talking

play14:54

about something else but uh what i'm

play14:57

trying to say is that if you are

play14:59

trying to become a consultant then then

play15:00

decide whether you want to focus on the

play15:02

technical side or not non-technical

play15:03

sides set side of things like you know

play15:06

the the business side

play15:07

all right so that is all that is all i

play15:09

wanted to talk about in this video i

play15:12

hope i hope i have given you some ideas

play15:14

these days i'm talking of course

play15:16

quite a lot about

play15:18

these things

play15:19

career options

play15:21

in

play15:22

atlassian

play15:24

atlassian field do let me know if you

play15:26

have any questions for me i think you

play15:27

have been sending me those questions but

play15:29

uh

play15:29

if you have more questions about carrier

play15:31

in general in this particular area in

play15:33

this particular domain

play15:35

i'll be more than happy to answer your

play15:36

questions and by the way you can always

play15:38

go to my website ravi sagar dot in

play15:40

slash support or visage if you find this

play15:43

contact button

play15:45

reach out to me i will answer your

play15:47

question

play15:48

all right

play15:49

thank you very much bye

Rate This

5.0 / 5 (0 votes)

Étiquettes Connexes
Atlassian ToolsCareer AdviceBusiness ConsultantTechnical ConsultantAgile MethodologyScrum MasterJira SoftwareProductivity TipsTeam CollaborationConsulting Roles
Besoin d'un résumé en anglais ?