DZone
Thanks for visiting DZone today,
Edit Profile
  • Manage Email Subscriptions
  • How to Post to DZone
  • Article Submission Guidelines
Sign Out View Profile
  • Post an Article
  • Manage My Drafts
Over 2 million developers have joined DZone.
Log In / Join
Refcards Trend Reports Events Over 2 million developers have joined DZone. Join Today! Thanks for visiting DZone today,
Edit Profile Manage Email Subscriptions Moderation Admin Console How to Post to DZone Article Submission Guidelines
View Profile
Sign Out
Refcards
Trend Reports
Events
Zones
Culture and Methodologies Agile Career Development Methodologies Team Management
Data Engineering AI/ML Big Data Data Databases IoT
Software Design and Architecture Cloud Architecture Containers Integration Microservices Performance Security
Coding Frameworks Java JavaScript Languages Tools
Testing, Deployment, and Maintenance Deployment DevOps and CI/CD Maintenance Monitoring and Observability Testing, Tools, and Frameworks
Partner Zones AWS Cloud
by AWS Developer Relations
Culture and Methodologies
Agile Career Development Methodologies Team Management
Data Engineering
AI/ML Big Data Data Databases IoT
Software Design and Architecture
Cloud Architecture Containers Integration Microservices Performance Security
Coding
Frameworks Java JavaScript Languages Tools
Testing, Deployment, and Maintenance
Deployment DevOps and CI/CD Maintenance Monitoring and Observability Testing, Tools, and Frameworks
Partner Zones
AWS Cloud
by AWS Developer Relations
The Latest "Software Integration: The Intersection of APIs, Microservices, and Cloud-Based Systems" Trend Report
Get the report
  1. DZone
  2. Culture and Methodologies
  3. Agile
  4. Writing Advice for Conference Proposals

Writing Advice for Conference Proposals

It's completely different from writing articles or papers.

Johanna Rothman user avatar by
Johanna Rothman
·
Jan. 07, 19 · Opinion
Like (2)
Save
Tweet
Share
15.60K Views

Join the DZone community and get the full member experience.

Join For Free

I'm a shepherd for the XP2019 and Agile2019 conferences. I read the proposals, offer feedback, and then shepherd the papers through to completion once we accept the proposals.

I love reading experiences. I'm a total sucker for them. Why? Because they're short stories that reflect the Satir Change Model, the image here.

If you're trying to write a proposal for a conference or have a tech story you want to tell to a live audience, consider framing the story this way:

  1. Start with the problems. What kinds of problems did you see? For an experience report, consider adding the initial state (x many teams, y products).
  2. What triggered the problem for a change?
  3. What did you try? What succeeded? What failed? Did what you try make the problem worse? When did you make things better?
  4. What is the new state?

If you're proposing a new talk or a workshop, consider One Startling Sentence for conference proposals:

  • First sentence: What's the problem?
  • Second sentence: Why is this problem a problem?
  • Third sentence: Startling answer.
  • Fourth sentence: Implication of the startling sentence.

I'm working on an agile management talk proposal. I think this is my abstract:

For too long, we've been told, "we don't need managers in agile." Too many managers believe that they either have no role in an agile approach, or they will be fired, or become obsolete. The truth is that agile managers hold the power of agile transformation because they create and refine the organization's culture. It's time to invite managers, help them see their place in an agile organization, and create an agile culture.

After this paragraph, I have subsequent paragraphs that tell you what you will learn.

I'm still working on this first paragraph. I invite you to offer me feedback.

Whatever you write for a conference proposal, start with the problems. Show us how things changed for the better and what we will learn.

If you want people like me to accept your proposals (and I'm part of a team, not the only decider), start with the problems and tell us what worked.

Conference proposals are a different writing beast than articles or columns or papers. Don't be coy. Don't give us a promise. Tell us the problems and what we will learn.

article writing agile Advice (programming)

Published at DZone with permission of Johanna Rothman, DZone MVB. See the original article here.

Opinions expressed by DZone contributors are their own.

Popular on DZone

  • 10 Things to Know When Using SHACL With GraphDB
  • 5 Steps for Getting Started in Deep Learning
  • Journey to Event Driven, Part 1: Why Event-First Programming Changes Everything
  • Microservices 101: Transactional Outbox and Inbox

Comments

Partner Resources

X

ABOUT US

  • About DZone
  • Send feedback
  • Careers
  • Sitemap

ADVERTISE

  • Advertise with DZone

CONTRIBUTE ON DZONE

  • Article Submission Guidelines
  • Become a Contributor
  • Visit the Writers' Zone

LEGAL

  • Terms of Service
  • Privacy Policy

CONTACT US

  • 600 Park Offices Drive
  • Suite 300
  • Durham, NC 27709
  • support@dzone.com
  • +1 (919) 678-0300

Let's be friends: