AgileDays'18: content - all over the head
We have been doing this conference for the 12th time in a row, and each time the careful selection of speakers and topics remains the same. Any speech is selected by the program committee. Let's try to show how everything works.
We already wrote in the previous post that earlier our program committee consisted of ScrumTrek employees. We ourselves selected reports and worked with speakers, but this year we have more than 200 applications for speeches, and it became clear that we need to expand.
9 topics have been announced on AgileDays 2018. Each topic is the future track of the conference. Each track has its own curator. Inside, we call him "track producer."
')
Meet:
Track “Agile for All”
Mikhail Podurets , Qiwi
Developed and tested aircraft software. In a flexible world since 2008. Was a scrum master and owner of the product. He went to consulting to help other organizations build effective processes. He worked mainly with large Western and Russian banks, telecom companies. He currently works at Qiwi.
Track "Agile in large products and programs"
Lilia Alekseeva , Sberbank
Agile Evangelist, Product Owner of the Agile Production Process, an expert in scaling flexibility in large corporations.
Track "Flexible Organizations"
Evgeny Jamalov , M.Video
He has been working in the IT industry for 18 years, starting with “enikeyschik”, developer, analyst, architect. Managerial experience lies in the areas of project, vendor, resource and release. Transformer, facilitator and mentor. He has extensive experience in project management, scrum-master and agile-coach.
Track "Agile in public administration"
Ivan Dubrovin , ScrumTrek
Agile coach ScrumTrek, leader and founder of the GOS-Agile movement, expert in Agile application in the public sector, a specialist in the field of Agile economics, a certified ICAgile trainer.
Track "Lean and Kanban"
Vasily Cheptsov , Avito
Engaged in development since 2001. He worked as a web designer, developer, technical / IT-director, system / business analyst, project / product manager.
Track "DevOps and Engineering Culture"
Sergey Baranov , ScrumTrek
15 years in business! Over the development, architecture, business development and start-ups. In ScrumTrek I came to develop the engineering direction, but it soon became clear - processes, engineering, culture, products - these are indivisible parts of a single whole. Currently, ScrumTrek is developing DevOps and working with large companies, helping them to implement changes leading to Business Agility.
Track “Agile Leadership and Scrum Mastery”
Alexey Yan , Sberbank
Agile coach, a former developer, product manager, scrum master. The last 4 years, it has launched agile teams and transformed organizations. Professional Scrum Master, Certified Scrum Product Owner, Certified Scrum Professional
Track "Motivation and Psychology in Agile"
Natalia Gulchevskaya , Consulting Group "Business Leadership"
ACC ICF Certified Coach, Svetlana Chumakova Prize Winner Leadership Coaching Awards 2017, Member of the Board of Directors of the Russian Section of the International Coaching Federation ICF 2014-2015
Track Product Management
Octoberry team
And it happens when the curator is not one person, but a team of people. In this case, the team of guys from Octoberry, who help companies make successful products and services and increase the expertise of product managers.
First of all - for the "purity" of the topic. The producer ensures that the reports correspond to the general concept of the track, which he, by the way, can clarify and change.
Technically, the system works like this: a request for a speech arrives at the site. On the board of the program committee, a card of a potential speaker is created automatically with a note about the chosen topic. The producer of the corresponding track receives notification of a new application. If the topic of the report corresponds to the stated topic of the track, the application is accepted to work.
Of course, alone, the producer physically cannot physically check all the reports, so we, in consultation with the rest of the program committee, also attract assistant reviewers. A reviewer is always an experienced speaker and competent expert.
We don’t hide information about revisions and producers anywhere. On the contrary, we proudly announce them on our conference website.
Inside, we call this process a review of the report. We will use this terminology here.
Presentation style
It is advisable that it be informal, as if you are communicating with your team or friends.
Illustrations, artifacts
We always recommend inserting photographs (boards, teams, meetings, etc.), screenshots (Jira, requirements, ekselek, etc.) into the presentation. In the presence of such artifacts, your report does not look like an empty theory, and it is easier for people to perceive information and “ground” it.
Format
One of the proven and effective is Story Telling. In this format, the report is based on the principle of stories or fairy tales: there is a main character who finds himself in a difficult situation, tries to get out of it, but he does not work, he reflexes, comes up with a solution, and it works. The presentation of cases is based on this principle. This style of presentation involves the participants, makes them empathize. But, of course, you can use other presentation formats. For example, if we are talking about a review report.
Hall involvement
It is advisable to periodically throw questions into the hall so that the participants turn on and think out the report. This allows for engagement. For example, feel free to ask the audience how they would act in such and such a situation, what tools they would use to solve such and such problems, etc.
Text minimum
Beaten advice, which is still little listened to :) In presentations, it is desirable to avoid a large amount of text, otherwise you put the conference participants to make a choice, either read the text or listen to the speaker. Try to use more visual images and short phrases in large print, fixing the main ideas.
And, perhaps most important, the report should have been interesting :)
For our speakers, we do special training in the evenings to help prepare ourselves even better and hone elocution skills.
When registering an application on the site, any speaker will get acquainted with our rules:
We do not consider:
In conclusion, the rules are the same for everyone and there are no exceptions, including the conference sponsors. All our sponsors know that you can’t just pay money and come with an advertising report or not go through a review on the basis that “we pay you money”. In fairness, all sponsors treat this with understanding and gratitude. It is important to explain in advance that a bad performance will be remembered much brighter than the sponsor's logo on badges and press will, which means that sponsorship money will be wasted.
We hope that this post will be useful both to our speakers and conference participants, who want to understand why the program turned out exactly the same, and brave people who are dreaming, and maybe are already preparing their own IT events.
Come to us on March 22 and 23! The program is very rich. Especially for Habr's readers 10% discount on promotional code HABRAD18 .
We already wrote in the previous post that earlier our program committee consisted of ScrumTrek employees. We ourselves selected reports and worked with speakers, but this year we have more than 200 applications for speeches, and it became clear that we need to expand.
9 topics have been announced on AgileDays 2018. Each topic is the future track of the conference. Each track has its own curator. Inside, we call him "track producer."
')
Meet:
Track “Agile for All”
Mikhail Podurets , Qiwi
Developed and tested aircraft software. In a flexible world since 2008. Was a scrum master and owner of the product. He went to consulting to help other organizations build effective processes. He worked mainly with large Western and Russian banks, telecom companies. He currently works at Qiwi.
Track "Agile in large products and programs"
Lilia Alekseeva , Sberbank
Agile Evangelist, Product Owner of the Agile Production Process, an expert in scaling flexibility in large corporations.
Track "Flexible Organizations"Evgeny Jamalov , M.Video
He has been working in the IT industry for 18 years, starting with “enikeyschik”, developer, analyst, architect. Managerial experience lies in the areas of project, vendor, resource and release. Transformer, facilitator and mentor. He has extensive experience in project management, scrum-master and agile-coach.
Track "Agile in public administration"
Ivan Dubrovin , ScrumTrek
Agile coach ScrumTrek, leader and founder of the GOS-Agile movement, expert in Agile application in the public sector, a specialist in the field of Agile economics, a certified ICAgile trainer.
Track "Lean and Kanban"Vasily Cheptsov , Avito
Engaged in development since 2001. He worked as a web designer, developer, technical / IT-director, system / business analyst, project / product manager.
Track "DevOps and Engineering Culture"
Sergey Baranov , ScrumTrek
15 years in business! Over the development, architecture, business development and start-ups. In ScrumTrek I came to develop the engineering direction, but it soon became clear - processes, engineering, culture, products - these are indivisible parts of a single whole. Currently, ScrumTrek is developing DevOps and working with large companies, helping them to implement changes leading to Business Agility.
Track “Agile Leadership and Scrum Mastery”
Alexey Yan , Sberbank
Agile coach, a former developer, product manager, scrum master. The last 4 years, it has launched agile teams and transformed organizations. Professional Scrum Master, Certified Scrum Product Owner, Certified Scrum Professional
Track "Motivation and Psychology in Agile"
Natalia Gulchevskaya , Consulting Group "Business Leadership"
ACC ICF Certified Coach, Svetlana Chumakova Prize Winner Leadership Coaching Awards 2017, Member of the Board of Directors of the Russian Section of the International Coaching Federation ICF 2014-2015
Track Product Management
Octoberry team
And it happens when the curator is not one person, but a team of people. In this case, the team of guys from Octoberry, who help companies make successful products and services and increase the expertise of product managers.
What the producer is responsible for
First of all - for the "purity" of the topic. The producer ensures that the reports correspond to the general concept of the track, which he, by the way, can clarify and change.
Technically, the system works like this: a request for a speech arrives at the site. On the board of the program committee, a card of a potential speaker is created automatically with a note about the chosen topic. The producer of the corresponding track receives notification of a new application. If the topic of the report corresponds to the stated topic of the track, the application is accepted to work.
Of course, alone, the producer physically cannot physically check all the reports, so we, in consultation with the rest of the program committee, also attract assistant reviewers. A reviewer is always an experienced speaker and competent expert.
We don’t hide information about revisions and producers anywhere. On the contrary, we proudly announce them on our conference website.
How we work with speakers
Inside, we call this process a review of the report. We will use this terminology here.
Why do you need a review?
- Understand whether the report is suitable for a conference or not: relevant, interesting, whether Agile and so on do not contradict the topic.
- Give feedback to the speaker on the content, style of presentation, presentation, so that the report is really cool.
How is the review
- We agree on a 30 minute call with the speaker. We ask him to prepare a draft presentation or at least empty slides with titles. This will help the speaker at a preliminary stage to think a little about his story.
- 5 minutes - acquaintance, story about the purpose of the review and format of the review.
- We usually tell the speaker that the purpose of the review is to help him make a cool report through feedback.
- 10 minutes - a short story speaker. At this time, it is better not to interrupt it and record feedback during these 10 minutes.
- 15 minutes - feedback feedback in the dialogue mode.
- If necessary, we agree on the next call.
What to look for when reviewing
Presentation style
It is advisable that it be informal, as if you are communicating with your team or friends.
Illustrations, artifacts
We always recommend inserting photographs (boards, teams, meetings, etc.), screenshots (Jira, requirements, ekselek, etc.) into the presentation. In the presence of such artifacts, your report does not look like an empty theory, and it is easier for people to perceive information and “ground” it.
Format
One of the proven and effective is Story Telling. In this format, the report is based on the principle of stories or fairy tales: there is a main character who finds himself in a difficult situation, tries to get out of it, but he does not work, he reflexes, comes up with a solution, and it works. The presentation of cases is based on this principle. This style of presentation involves the participants, makes them empathize. But, of course, you can use other presentation formats. For example, if we are talking about a review report.
Hall involvement
It is advisable to periodically throw questions into the hall so that the participants turn on and think out the report. This allows for engagement. For example, feel free to ask the audience how they would act in such and such a situation, what tools they would use to solve such and such problems, etc.
Text minimum
Beaten advice, which is still little listened to :) In presentations, it is desirable to avoid a large amount of text, otherwise you put the conference participants to make a choice, either read the text or listen to the speaker. Try to use more visual images and short phrases in large print, fixing the main ideas.
And, perhaps most important, the report should have been interesting :)
For our speakers, we do special training in the evenings to help prepare ourselves even better and hone elocution skills.
Formal requirements for reports
When registering an application on the site, any speaker will get acquainted with our rules:
- Compliance with at least one of the topics of the conference.
- Minimum theory, maximum case studies / practical experience.
- Focus on solving a single problem (or several related problems). Too general reports, such as “How Agile works with us,” will be rejected. Reports where there are no issues or advertising present will be rejected.
- If you have already had a similar report at a conference, you should explain to the program committee what the differences will be.
We do not consider:
- theoretical reports and reports in the spirit of “as I understood what Agile is”;
- reports of Agile-consultants without case studies and specifying the names of specific companies where these cases were;
- about your own pseudo-scrum;
- selfPR;
- obvious things, for example: scrum in a small studio for 6 people;
- silage scrum, for example: scrum in sales (unless they are on the supply chain of value).
In conclusion, the rules are the same for everyone and there are no exceptions, including the conference sponsors. All our sponsors know that you can’t just pay money and come with an advertising report or not go through a review on the basis that “we pay you money”. In fairness, all sponsors treat this with understanding and gratitude. It is important to explain in advance that a bad performance will be remembered much brighter than the sponsor's logo on badges and press will, which means that sponsorship money will be wasted.
We hope that this post will be useful both to our speakers and conference participants, who want to understand why the program turned out exactly the same, and brave people who are dreaming, and maybe are already preparing their own IT events.
Come to us on March 22 and 23! The program is very rich. Especially for Habr's readers 10% discount on promotional code HABRAD18 .
Source: https://habr.com/ru/post/349062/
All Articles