We are compiling a list of rules and common
definitions in
plain english.
Please help us!
See below for guidelines for contributing.
- One Subject/Topic/Request/Action Point per email.
- Don't hijack an email with one subject and reply with a totally different one. e.g. if the topic is "Training Policy" don't try to sidetrack the email to a conversation about "stationary ordering" (or what ever!). Just start a new/fresh email.
- Don't include people who don't need to be included. reply-to-all and CC'ing everyone for no reason wastes people's time.
- Conversely if the original sender of an email has included specific people in CC, its good practice to reply-to-all to ensure those people are kept informed. (yes this perpetuates an include everyone mistake but its better to keep people informed than have them feel "left out")
More detail: http://www.emailreplies.com (please add the ones you feel are important)
Its not a request unless its written.
If someone asks you to do something verbally, ask them to formalise the request before you start.
Take the initiative to create a story in the task tracker and send it to them to confirm you have the details correct.
Before a project/task can be started, the person taking on the task (maker) must confirm their understanding of the requirement(s) from the person who requested the task (requestor).
Don't accept a task you know you are unable to complete. If you do not have enough time or skills to deliver a task make that clear to the requestor and let her decide if its appropriate for you to do the work.
Yes, this contradicts the idea of "fake it till you make it" but it prevents people from making promises they can't keep (which makes everyone sad...)
We get paid when we:
- Solve a problem for someone.
- Save someone time (e.g. a cleaner)
- Provide a service
### What is Chargeable?
An task is only chargeable if it has been
a) Formally requested by the requestor.
b) the definition of "done" agreed prior to
starting the work/task.
c) The time required to complete the task has been
estimated before starting and both parties agree
the estimate is fair & reasonable.
d) The work is complete per the
definition of "done".
e) Any time exceeding the original estimate is
clearly & satisfactorily justified to the
requestor.
### Non-Chargeable Work
Work that has not been *formally requested by a requestor is *not chargeable.
The simple rule is: No end result, no payent.
The only people who get paid to read are code reviewers, editors and librarians; we are neither of these. If you chose to review a book for an author/publisher, don't expect to get paid; you are doing it for a free book. Unless you are writing detailed notes on the book and condensing it so that you can pass on the knowledge to others, you are reading to understand the topic covered in the book/article/tutorial and learn from the experience of the author. We get paid for implementing the knowledge gained through reading.
If a chef reads lots of recipe books but makes no food, how much would you pay for his/her services? You're not going to pay the chef for the delicious meal they read about, you'd starve.
If on the other hand you produce a detailed tutorial as the result of your reading - better than existing tutorials on that subject - that can be published on the company website, that is content and is therefore paid work.
Again the simple rule applies: Content is an end result, therefore it can be charged at a standard rate.
Unless otherwise agreed in writing before work starts, invoices for work should only be sent when the work is complete.
Time is the most precious thing people have. Wasting your own time is your decision. Wasting the time of others - either through laziness or negligence - is inexcusable.
Todo: this needs re-wording
Don't sit around waiting for tasks/instructions. If you don't have anything to do, offer to help someone. If you don't have a list of things to learn, get one.
### The Requestor Defines "Done" for the Task
Its the requestor
If you were hit by a bus, can someone else pick up your work? No? Its not done.
---
Everyone is encouraged to add rules which promote clearer communication, cooperation and creativity.
The process for adding/modifying a rule is simple.
Either:
a. Submit an issue (for discussion) on github: https://github.com/ideaq/rules/issues
or
b. Fork
this rules repository,
on github, add the rule and submit a
pull-request.
Avoid creating rules which reduce communication/innovation/creativity, cause unreasonable bureaucracy or silos.
Acceptance
Acceptance Criteria
Activity
- A person who constructs something by putting parts or material together
- A person or thing that creates or develops a particular thing
Excessively complicated administrative procedure.
Criteria
- A person who does something.
- A person who acts rather than merely
talking or thinking.
Documented
Documentation is a set of documents provided on paper, or online (e.g. email), or on digital or analog media.
Before a project/task can be started the requestor establishes the definition of when the work is done.
Estimate
Estimation
Formal
Formalise
The quality of being unwilling to work or use energy; idleness
A person or thing that makes or produces something.
The market rate (or "going rate") for goods or services is the usual price charged for them in a free market.
To promise more than is delivered.
Capable of being reproduced at a different time or place and by different people.
A formal message requesting something.
One who, or that which, makes a request.
- A thing that is needed or wanted.
- A thing that is compulsory; a necessary condition.
More than one requirement.
Motivated to do or achieve something because of one’s own enthusiasm or interest, without needing pressure from others.
A system, process, department, etc. that operates in isolation from others.
- A person who takes a specified thing
- The opposite of a maker. A person who takes more value than they create. (Proposed)
---
And remember:
