Rate your teamwork experience

Overview:

Action Plan contains 35 steps to Rate your teamwork experience.
Which level you identify with the most?
Level 0) You cannot express thoughts/ideas to peers. You have poor spelling and grammar.
Level 1) Your peers can understand what is being said. You have good spelling and grammar.
Level 2) You're able to effectively communicate with peers
Level 3) You're able to understand and communicate thoughts/design/ideas/specs in a unambiguous manner and you can adjust communication as per the context
  • Option #1: Identify as communicator Level 0
  • Option #2: Identify as communicator Level 1
  • Option #3: Identify as communicator Level 2
  • Option #4: Identify as communicator Level 3
Which level you identify with the most?
Level 0) You only use straight line code with copy paste for reuse
Level 1) You're able to break up problem into multiple functions
Level 2) You're able to come up with reusable functions/objects that solve the overall problem
Level 3) You're able to use appropriate data structures and algorithms and come up with generic/object-oriented code that encapsulate aspects of the problem that are subject to change.
  • Option #1: Identify as problem decomposition Level 0
  • Option #2: Identify as problem decomposition Level 1
  • Option #3: Identify as problem decomposition Level 2
  • Option #4: Identify as problem decomposition Level 3
Which level you identify with the most?
Level 0) You take the given requirements and codes to spec
Level 1) You come up with questions regarding missed cases in the spec
Level 2) You understand complete picture and come up with entire areas that need to be speced
Level 3) You're able to suggest better alternatives and flows to given requirements based on experience
  • Option #1: Identify as requirements gatherer Level 0
  • Option #2: Identify as requirements gatherer Level 1
  • Option #3: Identify as requirements gatherer Level 2
  • Option #4: Identify as requirements gatherer Level 3
Which level you identify with the most?
Level 0) You put all your files inside one folder
Level 1) You separate your code into logical folders.
Level 2) No circular dependencies, binaries, libs, docs, builds, third-party code all organized into appropriate folders
Level 3) Physical layout of source tree matches logical hierarchy and organization. The directory names and organization provide insights into the design of the system.
  • Option #1: Identify as source tree organizer Level 0
  • Option #2: Identify as source tree organizer Level 1
  • Option #3: Identify as source tree organizer Level 2
  • Option #4: Identify as source tree organizer Level 3
Which level you identify with the most?
Level 0) No evidence of organization within a file
Level 1) Your methods are grouped logically or by accessibility
Level 2) Your file is grouped into regions and well commented with references to other source files
Level 3) Your file has a license header, summary, well commented, consistent white space usage. All your code looks beautiful.
  • Option #1: Identify as code organization within a file Level 0
  • Option #2: Identify as code organization within a file Level 1
  • Option #3: Identify as code organization within a file Level 2
  • Option #4: Identify as code organization within a file Level 3
Which level you identify with the most?
Level 0) No thought given to organizing code across files
Level 1) Related files are grouped into a folder
Level 2) Each physical file has a unique purpose, for e.g. one class definition, one feature implementation etc.
Level 3) Code organization at a physical level closely matches design and looking at file names and folder distribution provides insights into design
  • Option #1: Identify as code organization across files Level 0
  • Option #2: Identify as code organization across files Level 1
  • Option #3: Identify as code organization across files Level 2
  • Option #4: Identify as code organization across files Level 3
Which level you identify with the most?
Level 0) You use mono-syllable names.
Level 1) You use good names for files, variables classes, methods etc.
Level 2) No long functions, comments explaining unusual code, bug fixes, code assumptions
Level 3) Code assumptions are verified using asserts, code flows naturally – no deep nesting of conditionals or methods
  • Option #1: Identify as code readability Level 0
  • Option #2: Identify as code readability Level 1
  • Option #3: Identify as code readability Level 2
  • Option #4: Identify as code readability Level 3
Action Plan estimates 7 minutes to Rate your teamwork experience.
Get Started    

Other Intentions: