DZone
Agile Zone
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
  • Refcardz
  • Trend Reports
  • Webinars
  • Zones
  • |
    • Agile
    • AI
    • Big Data
    • Cloud
    • Database
    • DevOps
    • Integration
    • IoT
    • Java
    • Microservices
    • Open Source
    • Performance
    • Security
    • Web Dev
DZone > Agile Zone > Puzzle Driven Development in Action

Puzzle Driven Development in Action

In PDD, we allow the programmer to cut corners and return puzzles back to the master file. These puzzles are assigned to other programmers, and so on, till they're fixed.

Yegor Bugayenko user avatar by
Yegor Bugayenko
·
Apr. 08, 17 · Agile Zone · Tutorial
Like (2)
Save
Tweet
5.39K Views

Join the DZone community and get the full member experience.

Join For Free

puzzle driven development is a methodology we've been practicing on our teams for more than seven years. using pdd, we delegate the responsibility of task decomposition to its performers, eliminating the role of a project manager. we've been using our proprietary software for that. a month ago, we made it public, open source, and free. it is available at 0pdd —a github-based chat bot.

image title

here is how you configure it, in two steps. first, you grant read-only access to @0pdd in github (either private or public repository).

second, you add a webhook to your github repository: http://www.0pdd.com/hook/github (with just a push event).

now, your repository is being watched by 0pdd . every time you git push something new, it does a git pull and retrieves your changes from github. then it runs pdd , a command line tool that scans the entire code base and finds all occurrences of @todo markers.

for all newly found markers, 0pdd will submit new issues to the github issue tracking section of your repository.

also, when you remove markers from your code base, 0pdd will immediately close issues it created.

now, when an issue is assigned to a programmer, we allow him or her to return incomplete code back to the master. if and when the code is not complete, we ask the programmer to leave @todo markers in the code, called "puzzles." later, these puzzles will be assigned to other programmers, and so on. eventually, the problem will be fixed when most puzzles are resolved.

0pdd helps you automate this process and provides a summary report of the current situation with all puzzles in the entire code base. you can even add a nice badge to your github repo:

pdd status

if you click it, you will see the full report of all puzzles currently present and previously seen.

this mechanism helps us in many projects. you can use it for free. it's an open-source ruby product; feel free to contribute .

Open source GitHub Programmer (hardware) Repository (version control) Task (computing) teams Decomposition (computer science) Software Webhook

Published at DZone with permission of Yegor Bugayenko. See the original article here.

Opinions expressed by DZone contributors are their own.

Popular on DZone

  • Saving Memory In Java: Making The Smallest Memory Footprint
  • Correlation Between Fast TTM and Containers
  • Getting Started With RSocket Kotlin
  • No-Code/Low-Code Use Cases in the Enterprise

Comments

Agile Partner Resources

X

ABOUT US

  • About DZone
  • Send feedback
  • Careers
  • Sitemap

ADVERTISE

  • Advertise with DZone

CONTRIBUTE ON DZONE

  • Article Submission Guidelines
  • MVB Program
  • 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:

DZone.com is powered by 

AnswerHub logo