Agile Agency Survey October 2017 (Responses Filtered)
 Share
The version of the browser you are using is no longer supported. Please upgrade to a supported browser.Dismiss

 
Comment only
 
 
ABCDEFGHIJKLMNOPQRSTUVWXYZAAABACADAEAFAGAHAIAJAKALAMANAOAPAQARASATAUAVAWAXAYAZBABBBCBDBEBFBGBHBIBJBKBLBMBNBOBPBQBRBSBTBUBVBWBXBYBZCACBCCCD
1
Timestamp
Which of the following processes do you use and how important are they to your team? [Scrum]
Which of the following processes do you use and how important are they to your team? [Kanban]
Which of the following processes do you use and how important are they to your team? [Waterfall]
Which of the following processes do you use and how important are they to your team? [ScrumBan]
Which of the following processes do you use and how important are they to your team? [Hybrid]
Which of the following processes do you use and how important are they to your team? [Other]
Which other processes do you use that are important to your team?
How strictly do you follow this process?
Have you adapted the process to fit your needs, if so how and why?
Describe your role within the team [Developer]
Describe your role within the team [Manager]
Describe your role within the team [PM / PO Proxy]
Describe your role within the team [UX / Designer]
Describe your role within the team [DevOps]
Describe your role within the team [Scrum Master]
Describe your role within the team [Other]
Describe your role(s) if missing
What is the size of your agency?
What is the size of your delivery team or your average team size?
Where does your team work?
How do you match teams and projects
Why do you choose to work this way?
On average, how often do you change the assignment of teams or projects
How much are these disciplines integrated or separated in your teams? [Frontend and Backend development]
How much are these disciplines integrated or separated in your teams? [Development & DevOps]
How much are these disciplines integrated or separated in your teams? [Development & Testing]
How much are these disciplines integrated or separated in your teams? [Development & UX/Design]
How much are these disciplines integrated or separated in your teams? [Scrum Master]
When do you do discovery
Describe your discovery/planning process
What has the top priority when you talk about project increments?
How does your team communicate? [Group meetings overall]
How does your team communicate? [Group meetings for the entire team]
How does your team communicate? [Group meetings for a subset of the team]
How does your team communicate? [1-on-1 meetings]
How does your team communicate? [Meetings with stakeholders]
How does your team communicate? [Overall written communication]
How does your team communicate? [Written communication in tickets]
How does your team communicate? [Written communication via chat (i.e. Slack)]
How does your team communicate? [Written communication in blog or wiki]
How does your team communicate? [Written communication in pull requests]
How long do your iterations go?
How much time does each team member spend every day? [Standups]
How much time does each team member spend in a two week cycle on the following? [Review]
How much time does each team member spend in a two week cycle on the following? [Retrospective]
How much time does each team member spend in a two week cycle on the following? [Planning]
Overall how much time do you spend? [Client work (billable)]
Overall how much time do you spend? [Client work (unbillable)]
Overall how much time do you spend? [Internal work]
Overall how much time do you spend? [Other, unknown]
What is most important to you and your team when it comes to scheduling time?
Who is involved in defining work? [Lead Developer]
Who is involved in defining work? [Any Developer]
Who is involved in defining work? [UX/Design]
Who is involved in defining work? [Client / Product Owner]
Who is involved in defining work? [PM / PO Proxy]
Who is involved in defining work? [The entire team together]
Share some insights about defining work/tickets
How important are these tools for organizing your work? [Epics]
How important are these tools for organizing your work? [User Stories]
How important are these tools for organizing your work? [Acceptance criteria]
How important are these tools for organizing your work? [Definition of Done]
How important are these tools for organizing your work? [Definition of Ready]
How important are these tools for organizing your work? [Tasks]
How important are these tools for organizing your work? [Releases/Versions]
How important are these tools for organizing your work? [Sprints]
How do you estimate?
Who does the estimations
How regularly does the team meet the client
How is communication between the team and the client handled
Remarks about how you and your team communicate best with your clients
How often does your team deploy code?
Which of these practices does your team use? [Peer reviews / code reviews]
Which of these practices does your team use? [Automated testing]
Which of these practices does your team use? [User testing]
Which of these practices does your team use? [Per-ticket branch test environments]
Which of these practices does your team use? [Pair programming]
Which of these practices does your team use? [Mob programming]
Which of these practices does your team use? [Automated deployments / Continuous integration]
Which of these practices does your team use? [Story mapping]
Which other agile practices do you use?
2
10/17/2017 13:55:23Our top priority
Somewhat in use
Somewhat in use
Somewhat in use
3I don't do that
I do this somewhat
I don't do thatI don't do thatI don't do thatI don't do that20-505
50% co-located and remote
Stable teams with multiple projects at a time
Once a quarter
Team members have a specialisation sometimes
They work in different teams
No separation at all
Team members have a specialisation mostly
Team members have a specialisation mostly
2
Two week sprints/iterations
15min1h2h30min50 - 75%<10%25 - 50%
Refines/grooms/specifies the ticket
Refines/grooms/specifies the ticket
Refines/grooms/specifies the ticket
Refines/grooms/specifies the ticket
Refines/grooms/specifies the ticket
Creates ticket, Refines/grooms/specifies the ticket, Estimates the ticket
Not used
Quite important
Very important
Estimation is done in story points based on complexity
A tech lead does high level estimates, the team estimates on a lower level
Less frequently2
Rolling / Whenever necessary
Very important
Somewhat in use
Very important
Somewhat in use
Somewhat in use
Somewhat in use
Very important
Somewhat in use
3
10/18/2017 16:35:28Our top priorityDoesn't fit usDoesn't fit us
Somewhat in use
Somewhat in use
Not evaluated
Unblocking issues for other teams or customers take priority, after a while even this is predictable and gets a place in scrum planning.
5
We've built custom dashboards on top of Redmine for each team so we can have a multi-project, multi-team scrum process while keeping the core values of scrum in mind such as facilitating the team where necessary as a scrum master and helping to unblock ourselves AND other teams in the company.
I don't do that
This is my focus
I don't do thatI don't do that
I do this somewhat
This is my focus
This is my focus
CTO50-1006
Mostly co-located with some degree of remote
Stable teams with multiple projects at a time
Because this is the fastest way for results in our case, reality is a mess, your process should help getting clarity in this mess but not ignore it.
Every month
Team members sometimes have a specialisation
Team members mostly have a specialisation
Team members mostly have a specialisation
They work in different teams
Team members mostly have a specialisation
3
This really depends on the customer. We try to convince the client about working agile and the benefits this brings but we can't convince all of them. For those we have a discovery and strategy phase for the full project, warning the customer this could lead to a more expensive project and longer delivery times.
5Not practiced
Mostly practiced
Mostly practiced
Mostly practiced
Somewhat practiced
Somewhat practiced
Mostly practiced
Mostly practiced
Regularly practiced
Somewhat practiced
Two week sprints/iterations
15min30min30min30min<10%<10%75-90%10% - 25%
Providing value while keeping our tech debt in a reasonable place
Creates ticket, Refines/grooms/specifies the ticket, Estimates the ticket, Other
Creates ticket, Refines/grooms/specifies the ticket
Other
Creates ticket, Refines/grooms/specifies the ticket
Creates ticket, Refines/grooms/specifies the ticket, Estimates the ticket
We have in each team an estimation engineer, scrum master and an architect. Everyone is responsible for doing architectures and estimations, bit the QA goes through these roles. The scrum master is responsible for the 2 weekly process while also being part of the development team
Somewhat important
Very importantVery importantLittle importantLittle importantVery important
Somewhat important
Very important
Both hours as story points, in transition
A tech lead does high level estimates, the team estimates on a lower level
Less frequently3
Rolling / Whenever necessary
Somewhat in use
Tried but failed
Somewhat in use
Not needed
Somewhat in use
UnknownActively in use
Somewhat in use
4
10/18/2017 16:49:06Our top priorityMostly in useDoesn't fit us
Somewhat in use
Not evaluatedNot evaluated4
Additional ceremonies: Sprint planning, Backlog pruning
I don't do that
This is my focus
I do this somewhat
I don't do thatI don't do that
I do this somewhat
I do this somewhat
Project Lead, Sales/Solutions
50-1007Mostly remote
Form a team when a new project starts
Best pairing of available resources with project types.
Less often
Team members mostly have a specialisation
Team members sometimes have a specialisation
Team members mostly have a specialisation
Team members mostly have a specialisation
Team members sometimes have a specialisation
2
Preliminary discovery in solutioning/estimating, initial discovery at start, additional discovery added per phase if needed
2
Regularly practiced
Regularly practiced
Regularly practiced
Regularly practiced
Regularly practiced
Regularly practiced
Regularly practiced
Somewhat practiced
Somewhat practiced
Regularly practiced
Two week sprints/iterations
10min30min30min30min25 - 50%25 - 50%10% - 25%<10%
work/life balance vis a vis time zone differences
Refines/grooms/specifies the ticket, Estimates the ticket
Estimates the ticket
Refines/grooms/specifies the ticket, Estimates the ticket
Creates ticket, Refines/grooms/specifies the ticket
Creates ticket, Refines/grooms/specifies the ticket
Refines/grooms/specifies the ticket, Estimates the ticket
Involvement across ticket lifespan evolves as project matures.
Very importantVery importantVery importantVery important
Quite important
Somewhat important
Very importantVery important
Estimation is done in story points based on complexity
The entire team does all estimations
More or once per week
3
Best organized teams have topic SMEs clients can communicate directly with for help with requirements and tickets. Higher volume requests become fixed office hours.
dev/multiple times daily; stage/1 or 2x weekly; prod/1 or 2x per 2week sprint
Somewhat in use
Very importantVery important
Somewhat in use
Somewhat in use
Somewhat in use
Very importantVery important
5
10/18/2017 18:24:40Mostly in useMostly in useDoesn't fit usOur top priorityMostly in use4
Always the customer decides which process works better and we adapt it to their needs considering their feedback. Customer first!
I do this somewhat
This is my focus
This is my focus
I do this somewhat
I do this somewhat
This is my focus
Janitor5-105Mostly remote
Form a team when a new project starts
Choose the best team that fits the project
Once a quarter
Team members mostly have a specialisation
Team members mostly have a specialisation
Team members mostly have a specialisation
Team members mostly have a specialisation
Team members mostly have a specialisation
5
Always learning from customers, team and market
5
Somewhat practiced
Not practiced
Somewhat practiced
Somewhat practiced
Somewhat practiced
Regularly practiced
Somewhat practiced
Somewhat practiced
Not practiced
Somewhat practiced
A week5min30min1h2h25 - 50%10% - 25%10% - 25%<10%
Get the most of our time
Creates ticket, Refines/grooms/specifies the ticket, Estimates the ticket
Creates ticket, Refines/grooms/specifies the ticket
Creates ticket, Refines/grooms/specifies the ticket
Being the most verbose possible
Somewhat important
Somewhat important
Somewhat important
Somewhat important
Somewhat important
Quite important
Somewhat important
Quite important
Estimation is done in days/hours
A tech lead does all estimates
More or once per week
3
Video conference
Rolling / Whenever necessary
Somewhat in use
Somewhat in use
Somewhat in use
Unknown
Somewhat in use
Unknown
Somewhat in use
Unknown
6
10/19/2017 0:45:47
Somewhat in use
Mostly in use3
This is my focus
10-203 or lessMostly remote
Stable teams with multiple projects at a time
Less often
Team members sometimes have a specialisation
Team members sometimes have a specialisation
Team members sometimes have a specialisation
Team members sometimes have a specialisation
2meetings3
Somewhat practiced
Somewhat practiced
Somewhat practiced
Regularly practiced
Somewhat practiced
Regularly practiced
Regularly practiced
Mostly practiced
Not practicedNot practicedA day5min30min30min30min> 90%<10%Creates ticketCreates ticketCreates ticketCreates ticketCreates ticketCreates ticket
Quite important
Quite important
Little importantLittle importantLittle important
Quite important
Quite important
Somewhat important
Estimation is done in days/hours
The entire team does all estimations
Less frequently1
About once a week
Somewhat in use
Tried but failedTried but failedActively in useNot neededUnknownTried but failedUnknown
7
10/19/2017 7:44:21Mostly in use
Somewhat in use
Somewhat in use
Mostly in useNot evaluatedNot evaluated4
Catered for fixed scope by introducing in scope and out of scope backlogs. Stories can be moved between each based on story point size.
I do this somewhat
This is my focus
I do this somewhat
This is my focus
This is my focus
50-1004
All co-located in an office
Form a team when a new project starts
Every month
Team members sometimes have a specialisation
Team members mostly have a specialisation
Team members sometimes have a specialisation
They work in different teams
Team members sometimes have a specialisation
3
Separation of discovery and definition defining AC). Discovery happens at the beginning and definition iteratively.
3
Somewhat practiced
Mostly practiced
Somewhat practiced
Somewhat practiced
Regularly practiced
Somewhat practiced
Regularly practiced
Regularly practiced
Regularly practiced
Regularly practiced
3 weeks15min1h30min4h75-90%25 - 50%25 - 50%
Creates ticket, Refines/grooms/specifies the ticket, Estimates the ticket
Creates ticket
Creates ticket, Refines/grooms/specifies the ticket
Creates ticketCreates ticket
Somewhat important
Very importantVery importantVery importantVery important
Somewhat important
Quite important
Quite important
Story points based on relative complexity first. Part of definition of ready is subtask breakdown with time estimates.
A tech lead does all estimates
Every two weeks
3
Rolling / Whenever necessary
Very important
Somewhat in use
Somewhat in use
Somewhat in use
UnknownUnknownVery important
Somewhat in use
8
10/19/2017 10:03:32Mostly in use
Somewhat in use
Somewhat in use
Not evaluated
Somewhat in use
Not evaluated2
I do this somewhat
I do this somewhat
I do this somewhat
I don't do that
I do this somewhat
I do this somewhat
5-103 or lessMostly remote
Stable teams with one project at a time
Once a quarter
Team members sometimes have a specialisation
They work in different teams
They work in different teams
They work in different teams
No separation at all
32
Mostly practiced
Mostly practiced
Somewhat practiced
Mostly practiced
Somewhat practiced
Regularly practiced
Mostly practiced
Somewhat practiced
Not practiced
Two week sprints/iterations
15min1h1h1h50 - 75%<10%<10%not tracked
Creates ticket, Estimates the ticket
Creates ticket, Refines/grooms/specifies the ticket, Estimates the ticket
Refines/grooms/specifies the ticket
Creates ticket, Refines/grooms/specifies the ticket
Creates ticket, Refines/grooms/specifies the ticket, Estimates the ticket
Not used
Somewhat important
Quite important
Not usedNot usedVery importantNot used
Somewhat important
Estimation is done in days/hours
A tech lead does high level estimates, the team estimates on a lower level
Every two weeks
2
Rolling / Whenever necessary
Somewhat in use
Somewhat in use
Very important
Somewhat in use
Tried but failedUnknownVery importantUnknown
9
10/19/2017 10:05:57Mostly in use
Somewhat in use
Doesn't fit usNot evaluatedNot evaluatedNot evaluated3
This is my focus
This is my focus
This is my focus
I do this somewhat
I do this somewhat
5-104
All co-located in an office
Form a team when a new project starts
Every month
Team members mostly have a specialisation
Team members sometimes have a specialisation
Team members sometimes have a specialisation
Team members mostly have a specialisation
No separation at all
3
Mostly practiced
Regularly practiced
Somewhat practiced
Regularly practiced
Regularly practiced
Regularly practiced
Regularly practiced
Regularly practiced
Somewhat practiced
Regularly practiced
Two week sprints/iterations
5min1h30min2h10% - 25%10% - 25%25 - 50%
Creates ticket, Refines/grooms/specifies the ticket, Estimates the ticket
Creates ticket, Refines/grooms/specifies the ticket, Estimates the ticket
Creates ticket, Refines/grooms/specifies the ticket, Estimates the ticket
Creates ticket
Estimates the ticket
Very important
Quite important
Somewhat important
Little importantLittle important
Somewhat important
Somewhat important
Quite important
Estimation is done in days/hours
A tech lead does high level estimates, the team estimates on a lower level
Less frequently3DailyVery importantActively in useActively in useActively in useNot neededUnknownVery important
10
10/19/2017 12:54:52Our top priority
Somewhat in use
Doesn't fit us
Somewhat in use
Not evaluatedNot evaluated3
Inspect abd adaot is the major point in scrum, thus at the end a process could look different to scrum
I don't do that
This is my focus
I do this somewhat
I don't do thatI don't do that
This is my focus
50-1005Mostly remote
Form a team when a new project starts
To be flexibel. Neverthless, we do have a one stable teM with several project for maintainance
Less often
Team members mostly have a specialisation
They work in different teams
They work in different teams
They work in different teams
They work in different teams
54
Regularly practiced
Regularly practiced
Regularly practiced
Mostly practiced
Regularly practiced
Mostly practiced
Regularly practiced
Regularly practiced
Regularly practiced
Regularly practiced
3 weeks15min1h1h4h50 - 75%<10%25 - 50%<10%
Creates ticket, Refines/grooms/specifies the ticket, Estimates the ticket
Creates ticket, Estimates the ticket
Refines/grooms/specifies the ticket
Refines/grooms/specifies the ticket
Refines/grooms/specifies the ticket
Refines/grooms/specifies the ticket, Estimates the ticket
Quite important
Very importantVery importantVery important
Quite important
Very importantVery importantVery important
Estimation is done in days/hours
A tech lead does high level estimates, the team estimates on a lower level
Less frequently3
Rolling / Whenever necessary
Very importantActively in useVery important
Somewhat in use
Somewhat in use
Unknown
Somewhat in use
Somewhat in use
11
10/19/2017 12:56:42Mostly in useOur top priority3
This is my focus
1-53 or lessFully remote
Form a team when a new project starts
Less often
Team members sometimes have a specialisation
Team members sometimes have a specialisation
No separation at all
They work in different teams
No separation at all
45
Somewhat practiced
Somewhat practiced
Somewhat practiced
Regularly practiced
Regularly practiced
Regularly practiced
Mostly practiced
Regularly practiced
Not practiced
Somewhat practiced
A week5min30min30min30min50 - 75%<10%<10%
Creates ticket, Refines/grooms/specifies the ticket, Estimates the ticket
Creates ticket, Estimates the ticket
Creates ticket, Estimates the ticket
Creates ticketCreates ticket
Somewhat important
Somewhat important
Little importantLittle importantLittle importantVery importantLittle important
Quite important
Estimation is done in days/hours
A tech lead does high level estimates, the team estimates on a lower level
Every two weeks
3
Rolling / Whenever necessary
Somewhat in use
Somewhat in use
Actively in useNot needed
Somewhat in use
Actively in useNot needed
12
10/19/2017 16:54:59
Somewhat in use
Somewhat in use
Somewhat in use
Our top priorityMostly in useNot evaluated
critique, automated testing, collaborative sketching
4
Yes. Our company is small and has a wide range of expertise levels - so mentorship and ownership of risk is shared by many people on the team. There has to be a certain level of teamship that encourages transparency. So, many of our processes are agile in it's implementation so as to be as flexible and reactive as possible.
This is my focus
I do this somewhat
I do this somewhat
I do this somewhat
20-505
50% co-located and remote
Form a team when a new project starts
Once a quarter
Team members sometimes have a specialisation
Team members sometimes have a specialisation
Team members sometimes have a specialisation
Team members mostly have a specialisation
Team members sometimes have a specialisation
43
Regularly practiced
Somewhat practiced
Regularly practiced
Mostly practiced
Somewhat practiced
Somewhat practiced
Somewhat practiced
Regularly practiced
Not practiced
Regularly practiced
Two week sprints/iterations
5min4h1h1h> 90%<10%<10%not tracked
Creates ticket, Refines/grooms/specifies the ticket, Estimates the ticket
Refines/grooms/specifies the ticket, Estimates the ticket
Refines/grooms/specifies the ticket
Creates ticket, Refines/grooms/specifies the ticket
Refines/grooms/specifies the ticket, Estimates the ticket
Quite important
Quite important
Quite important
Somewhat important
Little important
Quite important
Quite important
Quite important
Estimation is done in story points based on complexity
The entire team does all estimations
Every two weeks
2
About every two weeks
Actively in use
Somewhat in use
Unknown
Somewhat in use
UnknownUnknown
Somewhat in use
Unknown
13
10/19/2017 23:27:56Our top priorityMostly in use
Somewhat in use
Not evaluatedMostly in use
Sprint planning and retrospectives. Waterfall is only marked as "somewhat in use" because sometimes you end up in client-dictated situations which force more of that kind of workflow.
3
This is my focus
I do this somewhat
I do this somewhat
I don't do that
I do this somewhat
I do this somewhat
I don't do that50-1004Fully remote
Form a team when a new project starts
Different skills required for different projects. Scheduling.
Less often
Team members mostly have a specialisation
Team members mostly have a specialisation
No separation at all
They work in different teams
Team members mostly have a specialisation
25
Mostly practiced
Mostly practiced
Regularly practiced
Regularly practiced
Mostly practiced
Mostly practiced
Mostly practiced
Mostly practiced
Regularly practiced
Regularly practiced
Two week sprints/iterations
30min4h30min30min> 90%<10%10% - 25%not tracked
Refines/grooms/specifies the ticket, Estimates the ticket
Refines/grooms/specifies the ticket, Estimates the ticket
Refines/grooms/specifies the ticket, Estimates the ticket
Creates ticket, Refines/grooms/specifies the ticket, Estimates the ticket
Creates ticket, Refines/grooms/specifies the ticket, Estimates the ticket
Refines/grooms/specifies the ticket, Estimates the ticket
Somewhat important
Quite important
Very importantVery importantVery importantVery importantVery importantVery important
Estimation is done in story points based on effort
The entire team does all estimations
Each day for the daily standup
5
depends on the client
Very importantVery importantVery importantVery importantNot neededNot neededVery importantUnknown
14
10/20/2017 9:09:43Our top priority
Somewhat in use
Doesn't fit usNot evaluatedNot evaluatedNot evaluated4
I do this somewhat
This is my focus
This is my focus
I don't do thatI don't do that
I do this somewhat
I don't do that5-103 or less
50% co-located and remote
Form a team when a new project starts
For us it's better to change people within a project team between projects. We preffer that all people work with others in some point.
Every month
Team members mostly have a specialisation
Team members sometimes have a specialisation
Team members sometimes have a specialisation
They work in different teams
Team members sometimes have a specialisation
44
Somewhat practiced
Regularly practiced
Not practicedNot practiced
Somewhat practiced
Not practicedNot practiced
Somewhat practiced
Not practiced
Somewhat practiced
Two week sprints/iterations
5min4h1h1h75-90%10% - 25%10% - 25%
Refines/grooms/specifies the ticket, Estimates the ticket
Refines/grooms/specifies the ticket, Estimates the ticket
Refines/grooms/specifies the ticket
Creates ticket
Refines/grooms/specifies the ticket, Estimates the ticket
Not usedVery importantVery important
Somewhat important
Somewhat important
Very importantLittle importantVery important
Estimation is done in story points based on effort
The entire team does all estimations
Never1
Rolling / Whenever necessary
Very important
Somewhat in use
Somewhat in use
Unknown
Somewhat in use
UnknownVery importantUnknown
15
10/20/2017 13:25:14
Somewhat in use
Somewhat in use
Our top priority
Somewhat in use
Somewhat in use
Our top priority
Unfortunately the owner of the agency is making a complete mess and tries to control everything but makes everything very inefficient by doing so.
1
Owner of the agency doesnt believe and trust in agile principles, so we went back to normal old shitty waterfall
I don't do that
This is my focus
This is my focus
I do this somewhat
I don't do that
This is my focus
10-205
All co-located in an office
Form a team when a new project starts
the size of the agency and the volatile project size demands a individual project team
Once a quarter
Team members mostly have a specialisation
Team members mostly have a specialisation
Team members mostly have a specialisation
Team members mostly have a specialisation
Team members mostly have a specialisation
1
Discovery is actually not really done ;-((
1
Somewhat practiced
Somewhat practiced
Somewhat practiced
Not practicedNot practicedNot practicedNot practiced
Regularly practiced
Not practicedNot practiced
the efforts to set a timeframe for sprints were abonded after the owner articulated his disbelieve in sprints
15min30min30min50 - 75%10% - 25%<10%stay realisticOtherOtherOtherOtherOtherOther
unfortunatly the owner tries to control everything and defines the work to be done
Not usedNot usedNot usedNot usedNot usedLittle importantNot usedNot used
We don't do estimates
Doesn't applyNever1badly
About once a week
UnknownUnknownUnknownUnknownUnknownUnknownUnknownUnknown
We tried all these practices and i personally loved them, but the owner does not support the agile approach and wants to stick to the old fashioned way of waterfall projects due to fear of change
16
10/20/2017 13:48:27Our top priorityMostly in useDoesn't fit usDoesn't fit usDoesn't fit usAgile Scrum4
Agile is a guideline, naturally we have implemented it according to our business context. The level of Agile depends on the client. We prefer to sell sprints and be measured on value delivered than features per £. There is tension between project types - those clients who truly get Agile and those who come with an RFP listing features. The later is not ideally suited to Agile.
I don't do that
I don't do anything else
I don't do thatI don't do thatI don't do thatI don't do thatI don't do that
Company Director
50-1008 or more
Mostly co-located with some degree of remote
Best team to tailored to the project.
Most staff in one office and worked together before (long term staff retention). Having the right subject matter experts is more important than keeping teams together. Mixing teams up promotes knowledge transfer and reduces dependency upon any individual. Equals resilience for us, broader talent pool of available staff to work on client side. Our projects are usually long term (multiple years) so reduces burn out.
Once a quarter
Team members mostly have a specialisation
Team members mostly have a specialisation
Team members mostly have a specialisation
Team members mostly have a specialisation
Team members mostly have a specialisation
5
We do a short discovery phase but decisions are very high level, detail comes during sprint planning.
5
Mostly practiced
Mostly practiced
Mostly practiced
Somewhat practiced
Mostly practiced
Mostly practiced
Mostly practiced
Mostly practiced
Regularly practiced
Mostly practiced
Two week sprints/iterations
15min4h4h4h50 - 75%<10%10% - 25%
Staff and client satisfaction
Creates ticket, Estimates the ticket
Estimates the ticket
Estimates the ticket
Refines/grooms/specifies the ticket
Refines/grooms/specifies the ticket
Estimates the ticket
You have not mentioned Acceptance Criteria. This is written in collaboration between our QA and Stakeholders client side, ideally the product owner.
Very importantVery importantVery importantVery importantVery importantVery importantVery importantVery important
Estimation is done in story points based on complexity
A tech lead does high level estimates, the team estimates on a lower level
Each day for the daily standup
2
We do meet face to face which is important
Depends on the client. Usually at end of each sprint but can be as often as daily.
Very importantVery importantVery important
Somewhat in use
Somewhat in use
Somewhat in use
Very importantVery important
17
10/22/2017 10:02:25Mostly in use4
This is my focus
I do this somewhat
1-53 or lessMostly remote
Stable teams with multiple projects at a time
Less often
Team members mostly have a specialisation
Team members mostly have a specialisation
Team members sometimes have a specialisation
Team members sometimes have a specialisation
34Not practicedNot practiced
Somewhat practiced
Somewhat practiced
Somewhat practiced
Somewhat practiced
Mostly practiced
Regularly practiced
Somewhat practiced
Somewhat practiced
Two week sprints/iterations
10min1h30min30min> 90%<10%10% - 25%<10%
Creates ticket, Estimates the ticket
Creates ticket
Creates ticket, Estimates the ticket
Creates ticket
Creates ticket, Refines/grooms/specifies the ticket
Not usedLittle important
Quite important
Very important
Somewhat important
Quite important
Somewhat important
Estimation is done in days/hours
The entire team does all estimations
Less frequently4
About once a week
Somewhat in use
Very importantActively in use
Somewhat in use
Not neededNot neededVery importantNot needed
18
10/22/2017 11:38:53Doesn't fit usMostly in use
Somewhat in use
Somewhat in use
Somewhat in use
Not evaluatedgitlab workflow5no
I do this somewhat
This is my focus
I do this somewhat
I do this somewhat
I do this somewhat
I don't do that
This is my focus
1-53 or less
Mostly co-located with some degree of remote
Form a team when a new project starts
Need more people to have stable team sizes.
Every month
Team members mostly have a specialisation
Team members mostly have a specialisation
Team members mostly have a specialisation
Team members mostly have a specialisation
Team members sometimes have a specialisation
4
The product leaps from MVP to MVP.
5
Somewhat practiced
Somewhat practiced
Somewhat practiced
Regularly practiced
Regularly practiced
Not practiced
Regularly practiced
Regularly practiced
Not practicedNot practiced
Two week sprints/iterations
15min2h1h1h25 - 50%<10%50 - 75%not tracked
We still need a goog timetracker.
Estimates the ticket
Creates ticket
Refines/grooms/specifies the ticket
Refines/grooms/specifies the ticket
Creates ticket, Refines/grooms/specifies the ticket
Other
You need experience to estimate right.
Somewhat important
Little important
Quite important
Very importantVery important
Quite important
Quite important
Somewhat important
Estimation is done in story points based on effort
A tech lead does high level estimates, the team estimates on a lower level
Less frequently2
Separate brainstorm sessions with phones off at our office.
Rolling / Whenever necessary
Somewhat in use
Somewhat in use
Somewhat in use
Somewhat in use
UnknownUnknown
Somewhat in use
Tried but failed
19
10/22/2017 11:45:09
Somewhat in use
Mostly in use
Somewhat in use
Not evaluatedNot evaluatedNot evaluated2
This is my focus
I do this somewhat
I do this somewhat
I don't do that
I do this somewhat
I don't do thatI don't do that5-104
All co-located in an office
Stable teams with multiple projects at a time
Every two weeks or more often
Team members sometimes have a specialisation
Team members sometimes have a specialisation
No separation at all
They work in different teams
Team members sometimes have a specialisation
22
Somewhat practiced
Mostly practiced
Regularly practiced
Mostly practiced
Regularly practiced
Regularly practiced
Somewhat practiced
Somewhat practiced
Regularly practiced
Not practiced
Two week sprints/iterations
10min2h1h4h50 - 75%25 - 50%10% - 25%10% - 25%
Creates ticket, Refines/grooms/specifies the ticket
Creates ticket, Refines/grooms/specifies the ticket
OtherOther
Creates ticket, Refines/grooms/specifies the ticket
Estimates the ticket
Not used
Somewhat important
Quite important
Very importantNot used
Somewhat important
Quite important
Somewhat important
Estimation is done in days/hours
A tech lead does high level estimates, the team estimates on a lower level
More or once per week
2
Rolling / Whenever necessary
Actively in useVery important
Somewhat in use
Actively in useActively in useUnknownVery importantUnknown
20
10/22/2017 13:42:35Doesn't fit us
Somewhat in use
Not evaluatedNot evaluated
Somewhat in use
Doesn't fit us2
This is my focus
20-508 or more
All co-located in an office
Stable teams with multiple projects at a time
Less often
Team members mostly have a specialisation
No separation at all
Team members mostly have a specialisation
They work in different teams
No separation at all
41
Somewhat practiced
Mostly practiced
Regularly practiced
Not practiced
Regularly practiced
Somewhat practiced
Somewhat practiced
Somewhat practiced
Somewhat practiced
Not practicedLonger15min2h50 - 75%10% - 25%10% - 25%<10%Other
Creates ticket, Refines/grooms/specifies the ticket, Estimates the ticket
Other
Creates ticket, Refines/grooms/specifies the ticket
Creates ticket, Refines/grooms/specifies the ticket
Estimates the ticket, Other
Somewhat important
Somewhat important
Not usedNot usedNot usedLittle importantNot usedNot used
Estimation is done in days/hours
A tech lead does high level estimates, the team estimates on a lower level
Less frequently1
Rolling / Whenever necessary
Somewhat in use
Actively in useNot neededUnknownUnknownUnknownUnknown
21
10/23/2017 11:33:00Mostly in useMostly in useDoesn't fit usNot evaluatedNot evaluatedMostly in use
I use a few things out of Scrum and a few out of DSDM
2
It tends to alter a little each time, depending on the client.
This is my focus
I do this somewhat
I do this somewhat
I don't do that
I do this somewhat
I do this somewhat
1-53 or lessFully remote
Form a team when a new project starts
Once a quarter
Team members mostly have a specialisation
Team members sometimes have a specialisation
Team members sometimes have a specialisation
Team members sometimes have a specialisation
Team members sometimes have a specialisation
34
Regularly practiced
Regularly practiced
Somewhat practiced
Somewhat practiced
Mostly practiced
Regularly practiced
Mostly practiced
Somewhat practiced
Not practiced
Somewhat practiced
Two week sprints/iterations
10min2h1h4h50 - 75%not tracked25 - 50%<10%
Creates ticket, Refines/grooms/specifies the ticket, Estimates the ticket
Quite important
Quite important
Quite important
Somewhat important
Very importantLittle important
Somewhat important
Quite important
Estimation is done in story points based on complexity
The entire team does all estimations
More or once per week
2
Rolling / Whenever necessary
Somewhat in use
Somewhat in use
Actively in useActively in use
Somewhat in use
UnknownVery important
Somewhat in use
22
10/23/2017 22:45:34Our top priorityOur top priorityDoesn't fit usDoesn't fit usDoesn't fit usDoesn't fit us4I don't do that
This is my focus
I don't do thatI don't do thatI don't do that
I don't do anything else
I don't do that
DevOps is not a role!
20-506
Mostly co-located with some degree of remote
Stable teams with one project at a time
Every month
Team members sometimes have a specialisation
They work in different teams
No separation at all
Team members mostly have a specialisation
No separation at all
32
Somewhat practiced
Regularly practiced
Not practiced
Regularly practiced
Regularly practiced
Regularly practiced
Regularly practiced
Regularly practiced
Regularly practiced
Two week sprints/iterations
15min2h2h4h50 - 75%25 - 50%10% - 25%
Creates ticket, Refines/grooms/specifies the ticket, Estimates the ticket
Creates ticket, Refines/grooms/specifies the ticket, Estimates the ticket
Creates ticket, Refines/grooms/specifies the ticket, Estimates the ticket
Creates ticket, Refines/grooms/specifies the ticket
Creates ticket, Refines/grooms/specifies the ticket
Refines/grooms/specifies the ticket
Somewhat important
Very importantVery important
Quite important
Quite important
Somewhat important
Little importantVery important
Estimation is done in story points based on effort
The entire team does all estimations
Every two weeks
2
About every two weeks
Actively in use
Somewhat in use
Tried but failedActively in use
Somewhat in use
UnknownUnknown
Somewhat in use
23
10/24/2017 15:56:28Our top priority
Somewhat in use
Doesn't fit usNot evaluatedMostly in useHolacracy, XP4I don't do thatI don't do that
I do this somewhat
I don't do that
I do this somewhat
This is my focus
I don't do that100+5
All co-located in an office
Form a team when a new project starts
Stable teams are, well, stable. Whenever we have to make ad-hoc teams for new projects, it is kind of a hassle in the beginning
Once a quarter
Team members mostly have a specialisation
Team members mostly have a specialisation
No separation at all
Team members mostly have a specialisation
Team members mostly have a specialisation
3
A lot of discovery is done upfront (UX) and within iteration time (for the following sprint)
5
Regularly practiced
Regularly practiced
Regularly practiced
Regularly practiced
Regularly practiced
Regularly practiced
Regularly practiced
Regularly practiced
Regularly practiced
Regularly practiced
Two week sprints/iterations
15min2h1h2h50 - 75%<10%10% - 25%not tracked
Part time work needs a good planning
OtherOtherCreates ticket
Refines/grooms/specifies the ticket, Estimates the ticket
Somewhat important
Very important
Quite important
Quite important
Quite important
Quite important
Somewhat important
Very important
Estimation is done in story points based on complexity
The entire team does all estimations
More or once per week
4
Dedicated Slack channel with team and client persons
About once a week
Very importantActively in use
Somewhat in use
Somewhat in use
Actively in use
Somewhat in use
Actively in use
Somewhat in use
24
10/24/2017 17:40:09Mostly in use
Somewhat in use
Mostly in useNot evaluatedOur top priorityNot evaluated
It's not that "Hybrid" is our top priority, but due to circumstances it is what is mostly used in our company.
2
Usually the pre-conditions don't allow to follow a strict scrum process. With our clients, in 90% they want a fixed price offer, and we have a fix scope and a fix deadline. So it's waterfall in the end, but we try to be as agile as possible within those borders - what sometimes works quite good, if at least one of the points is a bit flexible (budget, time, scope), and sometimes doesn't work at all (when the client thinks that being agile just allows him to put more and more into scope).
I don't do that
I don't do anything else
I do this somewhat
I don't do thatI don't do that
I do this somewhat
100+5
Mostly co-located with some degree of remote
More or less stable teams with multiple projects at a time
As we don't have a fixed team for maintenace projects, usually a dev has one main project where she/he's working on, but also 1-2 projects where she/he has to work on older projects like a day every two weeks.
Then it also depends on the knowledge and specialization of people how a team will be staffed, but in the end we try to keep it as stable as possible
Once a quarter
They work in different teams
They work in different teams
They work in different teams
They work in different teams
Team members sometimes have a specialisation
3
As said before, this depends a lot on the project. If the client wants a fixed price offer, we usually have a phase for doing requirements engineering/planning - ideally with some workshops together with the client. If the client is more flexible, we do some top-level planning in the beginning and detailed planning during backlog-refinement and planning during/before the sprint.
2
Mostly practiced
Mostly practiced
Mostly practiced
Mostly practiced
Regularly practiced
Somewhat practiced
Mostly practiced
Mostly practiced
Mostly practiced
Mostly practiced
Two week sprints/iterations
15min2h1h2h50 - 75%10% - 25%10% - 25%<10%
People should have the chance to work without too many distraction, so bookings should be rather in a bigger chunk than split above several days. Meetings should be held in the morning, so that in the afternoon the devs can work without any interruptions (or the little as possible). Devs can't be booked 100% as it's important to have some buffer time for unexpected stuff. (is the question meant like that?)
Creates ticket, Refines/grooms/specifies the ticket, Estimates the ticket
Refines/grooms/specifies the ticket, Estimates the ticket
Creates ticket, Refines/grooms/specifies the ticket, Estimates the ticket
Creates ticket, Refines/grooms/specifies the ticket
Creates ticket, Refines/grooms/specifies the ticket
Estimates the ticket
Again - depending on the project/the client and the PM. We had clients that created and defined tickets together with the PO at our side, so that they could be specified during planning and then estimated by the devs. Sometimes PM is doing it, and sometimes this is done by the lead dev (if PM/PO isn't able to do it). Estimation depends a bit on the time pressure and the team size. If possible we estimate with the whole team. But sometimes we only have the lead dev and the dev who is going to implement the feature estimate.
Very importantVery importantVery important
Quite important
Quite important
Very important
Quite important
Very important
Depends on the project - sometimes estimation is done in days/hours, sometimes in SP based on complexity
See above, depending on the project
Depends a lot on the client: In some projects client joins the daily, in some the review/planning, in some there's a kickoff and some random meetings every some weeks
2
Again, it depends a lot on the project. If we work without involvement of the IT of the client, I think it's best if communication is mainly done per PM/PO, and that the team only communicates with the client during planning/review or in Jira tickets. If there's technical involvement from the client side, it should work as described above, + the tech lead should be in constant communication with the tech lead of the client. Only if we work really closely together with the IT of a client I would prefer that the communication is just like within our team, so that all devs talk with each other. If the communication is too mixed, especially between our devs and clients' PM, it can happen that the devs end up in a situation where they feel uncomfortable because they don't know how to react. So that's something I like to avoid.
Again, depends a lot on the project. There are projects with deployments whenever needed, and there are project with more or less fix release cycles where we deploy like every two weeks
Very important
Somewhat in use
Very important
Somewhat in use
Tried but failedUnknownVery importantUnknown
25
10/26/2017 13:20:16
Somewhat in use
Somewhat in use
Mostly in useNot evaluatedOur top priorityNot evaluated4
This is my focus
I don't do that
I do this somewhat
I don't do that
I do this somewhat
I do this somewhat
100+7
Mostly co-located with some degree of remote
Stable teams with multiple projects at a time
Once a quarter
Team members mostly have a specialisation
Team members mostly have a specialisation
They work in different teams
They work in different teams
Team members mostly have a specialisation
22
Somewhat practiced
Somewhat practiced
Regularly practiced
Regularly practiced
Somewhat practiced
Regularly practiced
Mostly practiced
Mostly practiced
Somewhat practiced
Somewhat practiced
Two week sprints/iterations
10min4h30min4h> 90%<10%<10%not tracked
Creates ticket, Refines/grooms/specifies the ticket, Estimates the ticket
Refines/grooms/specifies the ticket, Estimates the ticket
OtherCreates ticketCreates ticket
Refines/grooms/specifies the ticket, Estimates the ticket
Somewhat important
Very important
Quite important
Somewhat important
Somewhat important
Quite important
Quite important
Somewhat important
Estimation is done in days/hours
A tech lead does high level estimates, the team estimates on a lower level
More or once per week
2
Rolling / Whenever necessary
Actively in use
Somewhat in use
Very important
Somewhat in use
Somewhat in use
Not needed
Somewhat in use
Somewhat in use
26
10/26/2017 17:37:50
Somewhat in use
Somewhat in use
Somewhat in use
Not evaluatedNot evaluatedMostly in use
Whatever makes sense for them depending on the individuals, the client and the project context
1
Like design, the best process is invisible. If it feels natural you know you found the best way. We don't try to fit individuals, clients and projects into a process but find the right process for each.
This is my focus
I do this somewhat
I do this somewhat
I do this somewhat
I do this somewhat
I do this somewhat
I do this somewhat
Researcher, Sales
20-506
Mostly co-located with some degree of remote
Stable teams with one project at a time
To avoid to have to fit people into a process. Processes are to regulate how to work together. The more you work together the less you need structures and the more you know what works best for you naturally
Team members mostly have a specialisation
No separation at all
No separation at all
Team members mostly have a specialisation
No separation at all
1
With the client and stakeholders. Workshops / interviews
5
Regularly practiced
Regularly practiced
Regularly practiced
Regularly practiced
Regularly practiced
Somewhat practiced
Somewhat practiced
Regularly practiced
Somewhat practiced
Regularly practiced
Whatever makes sense for the project
2h75-90%not trackednot trackednot tracked
All client work is billable.
Creates ticketCreates ticketCreates ticketCreates ticketCreates ticketCreates ticket
We don't estimate tickets. We don't strickly write tickets for each task. Each tasks is a seperate branch though (assuming you talk about dev)
Quite important
Not usedNot usedNot usedNot used
Somewhat important
Quite important
Not used
Only for the offer
The entire team does all estimations
More or once per week
5
We don't have POs or PMs. Designers and developers talks directly to the client, stakeholders and their developers
DailyVery importantVery importantVery importantVery importantActively in use
Somewhat in use
Very importantUnknown
27
10/31/2017 22:24:21Mostly in useNot evaluatedDoesn't fit usDoesn't fit us
Somewhat in use
Somewhat in use
Agency Agile2
This is my focus
I do this somewhat
I do this somewhat
50-1008 or more
Mostly co-located with some degree of remote
Stable teams with multiple projects at a time
Less often
No separation at all
Team members sometimes have a specialisation
No separation at all
Team members sometimes have a specialisation
No separation at all
22
Somewhat practiced
Regularly practiced
Somewhat practiced
Somewhat practiced
Regularly practiced
Somewhat practiced
Mostly practiced
Mostly practiced
Somewhat practiced
Not practiced
Two week sprints/iterations
30min1h30min30min50 - 75%<10%<10%<10%
Refines/grooms/specifies the ticket
Creates ticket, Estimates the ticket
Somewhat important
Very important
Quite important
Little importantNot usedNot used
Quite important
Very important
Estimation is done in days/hours
The entire team does all estimations
More or once per week
3
About every two weeks
Actively in use
Somewhat in use
Tried but failed
Somewhat in use
Not neededNot neededActively in useActively in use
28
11/9/2017 15:48:42Mostly in use
Looking into switching to Scrum.
3
This is my focus
I do this somewhat
1-53 or less
All co-located in an office
There is only one team.
We only have three members in the Web Office.
Every month
No separation at all
No separation at all
Team members mostly have a specialisation
55
Mostly practiced
Mostly practiced
Somewhat practiced
Somewhat practiced
Somewhat practiced
Mostly practiced
Mostly practiced
Mostly practiced
Not practicedNot practicedMonthly5min30min30min30minnot trackednot trackednot trackednot tracked
Creates ticket, Refines/grooms/specifies the ticket, Estimates the ticket
Creates ticket, Estimates the ticket
Creates ticket, Estimates the ticket
Creates ticket, Estimates the ticket
Not usedNot usedNot usedNot usedNot usedVery importantNot usedLittle important
Estimation is done in days/hours
The entire team does all estimations
Less frequently3
Rolling / Whenever necessary
Somewhat in use
Somewhat in use
Somewhat in use
Very important
Somewhat in use
UnknownUnknownUnknown
29
11/9/2017 19:18:02Mostly in useMostly in useDoesn't fit usNot evaluatedNot evaluatedNot evaluated2Small team
This is my focus
I do this somewhat
I don't do thatI don't do that
I do this somewhat
I don't do that
I do this somewhat
Architect1-56
Mostly co-located with some degree of remote
Form a team when a new project starts
Mostly free agents who come and go
Less often
Team members mostly have a specialisation
Team members mostly have a specialisation
Team members mostly have a specialisation
Team members mostly have a specialisation
Team members sometimes have a specialisation
41
Somewhat practiced
Not practiced
Somewhat practiced
Regularly practiced
Regularly practiced
Somewhat practiced
Mostly practiced
Regularly practiced
Not practiced
Somewhat practiced
Two week sprints/iterations
5min1 day30min4h50 - 75%<10%10% - 25%not tracked
Creates ticket, Refines/grooms/specifies the ticket, Estimates the ticket
Creates ticket, Refines/grooms/specifies the ticket, Estimates the ticket
Estimates the ticket
Creates ticket, Refines/grooms/specifies the ticket
Little importantLittle important
Quite important
Little importantNot used
Somewhat important
Not used
Somewhat important
Estimation is done in days/hours
The entire team does all estimations
More or once per week
4Chat
About every two weeks
Tried but failed
Somewhat in use
Very importantTried but failedUnknownNot neededActively in useNot needed
30
11/9/2017 20:46:24
Somewhat in use
Somewhat in use
Somewhat in use
3
This is my focus
I do this somewhat
QA10-203 or lessMostly remote
Form a team when a new project starts
It sees to allow us to work faster. It lets us match the team to the project. Upside is potential for cross-fertilization. Downside is potential for pigeonholing and not giving people work that they have not done before.
Once a quarter
No separation at all
Team members sometimes have a specialisation
Team members mostly have a specialisation
They work in different teams
Team members mostly have a specialisation
3
There is no such thing as doing it all up front, so no need to pretend that it's possible :-) We are pretty flexible, some projects have relatively little definition at the outset and a freewheeling blue-sky iterative process, in other cases we try to keep a lid on things but this would typically be when we are porting / migrating an existing site to a new platform without redesign
2
Somewhat practiced
Mostly practiced
Not practiced
Somewhat practiced
Regularly practiced
Somewhat practiced
Mostly practiced
Regularly practiced
Not practiced
Regularly practiced
Two week sprints/iterations
15min1h1h2h25 - 50%<10%10% - 25%10% - 25%
managing expectations
Creates ticket, Refines/grooms/specifies the ticket
Refines/grooms/specifies the ticket
Creates ticket, Refines/grooms/specifies the ticket
Estimates the ticket
Defining "done" and criteria for moving tickets needs to be done at the beginning of each project / for each team
Somewhat important
Somewhat important
Quite important
Quite important
Somewhat important
Quite important
Somewhat important
Very important
Mostly in hours, but sometimes not at all. I think we'd like to do more work without direct estimates.
The entire team does all estimations
Always for reviews, but some clients have also been in planning meetings. One client insisted on being in daily standups, which meant we had the real standup beforehand then the sham standup with the client.
3
We like to have an open communication protocol and as long as clients are respectful ( and they generally are) that works very well and saves time. Typically this is in tickets or a Slack room. Keep all communication visible to the agency PO is important.
Rolling / Whenever necessary
Very important
Somewhat in use
Unknown
Somewhat in use
UnknownUnknown
Somewhat in use
Unknown
31
11/10/2017 10:26:58Our top priority
Somewhat in use
Doesn't fit us
Somewhat in use
Somewhat in use
Not evaluated4I don't do that
I do this somewhat
I don't do thatI don't do that
I do this somewhat
This is my focus
I do this somewhat
10-205
Mostly co-located with some degree of remote
Stable teams with multiple projects at a time
Less often
No separation at all
Team members sometimes have a specialisation
Team members sometimes have a specialisation
Team members sometimes have a specialisation
They work in different teams
44
Regularly practiced
Regularly practiced
Not practiced
Regularly practiced
Regularly practiced
Mostly practiced
Regularly practiced
Mostly practiced
Somewhat practiced
Somewhat practiced
A week15min2h4h2h50 - 75%10% - 25%25 - 50%10% - 25%
Creates ticket, Refines/grooms/specifies the ticket, Estimates the ticket
Creates ticket, Refines/grooms/specifies the ticket, Estimates the ticket
Creates ticket, Refines/grooms/specifies the ticket, Estimates the ticket
Creates ticket, Refines/grooms/specifies the ticket, Estimates the ticket
Little importantVery important
Somewhat important
Somewhat important
Somewhat important
Little importantLittle importantVery important
Estimation is done in story points based on effort
The entire team does all estimations
More or once per week
4Slack
Rolling / Whenever necessary
Actively in use
Somewhat in use
Somewhat in use
Unknown
Somewhat in use
UnknownActively in use
Somewhat in use
Project Canvas
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
Loading...
 
 
 
Sheet1
 
 
Main menu