Trello

공대 연구실에서의Trello 를 이용한 작업 , 협업 , 보고

Understanding concept and culture behind

trello Leaving good legacy Making the best culture for our laboratory Let’s help each other

For our bright future And to be a self-organizing researcher/devel-

oper/laboratory

Purpose

Organizing tool

GTD = Get Things Done (not same as to-do list) Task board: whiteboard and Post-it Idea note

Online collaboration tool Job assignment Priority Schedule and Progress report

For manager or boss?

NOPE!! But there are side benefits. Silver bullet or Cure-all?

Maybe…but mostly it’s not. Additional work to do?

Depends on situation and your boss/manager

Misapprehension

Research and DEVELOPMENT

Waterfall vs. Agile View of programming

Building an architecture vs. Gardening Working style

Plan everything first vs. Experience and then adjust

Misc. Sync to boss vs. Async with free will Spec & Docs vs. Problem solving

HUGE Differences

Analogy

How works done?

Most works for satisfaction of a boss/manager are not helpful much for people in charge. Actu-ally, it’s waste of time

Key scheduling con-cept

Divide Prioritize Do Learn Adjust … Divide Prioritize Do Learn Adjust ……

Caution: Don’t forget the GOAL!!!

If not think deeply, can not divide well. THINK! THINK! THINK! THINK! THINK! THINK! THINK!

Make things apart

FYI

Chicken and Pig analogy Each individual has different skill sets, schema,

experiences, situation, … So, there is no universal easy thing.

Tips for focused and concise meeting Get rid of chairs!!!

Surplus (esp. time) is good for all Chance to see bigger picture and to learn useful

skill for future.

Before we start…

Define goal

Express with one phrase or one sentence. If can’t, it’s too big. Make it small.

Share consensus Mutual understanding of the goal, problem, necessity, etc.

Big thing -> small things Little big thing matters Get things done!

Prioritize things Do more important things first

Share progress and dynamically manage jobs Here is a secrete!

Philosophy

Board - Project List – Schedule and more Card – Tasks to be done within 1~3 days

Comment opinions, obstacles, ideas, and progress Job assignment Schedule (with due) Priority (with order or label) Attachment (upload materials)

Checklist – GTD (Each list should be done within 0.5 ~ 4h)

Don’t fix anything. Thinks change. Flexibility is good

How to do?

To Do

Tasks to be done (just log them) Describe each task (What? Why? How? Who? When?)

Doing (use due and assignment) GTD (list up all small things to do and check done)

Done Leave for you (self-satisfaction) and others (progress

report). Additional list you want

Ex) Issue, reference, study, idea, and so on.

List

You can use many features

Description – define your task Comment – logs are always valuable. Asynchronous

communication doesn’t interrupt anybody. Attachment – images and files can be uploaded Due day – schedule your tasks Job assignment – add other people Vote – good? Vote (new feature) Priority – Order and Colored label

Archive Manage cards by archiving them. (it’s not deletion)

Card

Get things done

List all your small works related to the task Order them later with priority or logical se-

quence If done, check it one by one. If changed priority, just reorder them Dynamically add/remove/modify/reorder small

works

Checklist

Make things small Do them one by one Get things done! Share progress Organize all dynamically Helper tool for persons in charge Need boss’s deep understanding

Summary

Don’t zip project files for version control

Use version control system (Git or mercurial) Don’t email with attachment

Use dropbox-like services Don’t set meaningless meeting

Use asynchronous communication tool (com-ment and vote)

Daily short standup meeting Simply say done, doing, to do, and FEELING

Need scrum master?

For better work