Changes

Jump to: navigation, search

Engagement/Integrated Marketing/Definitions

340 bytes added, 17:28, 27 March 2014
no edit summary
The following are definitions that we will use throughout all of the process documentation to allow all of us to have the same common understanding and language. Each definition may contain examples and what form it should be in.
 
== Artifacts ==
 
Commonly this is called project artifacts and these are all of the tangible items that make up a project and they include most of the items listed here. They are also the specific to a project and include items like UX diagrams, test suites, server architecture.
 
Form: tangible aspects of a project.
== Block ==
A block or typically called a blocker is some action or deliverable that is preventing the completion of another task. An example of a blocker is imagine you were creating a website and you have designs and some code complete, but you are waiting on IT to provide servers to host it. You would say that IT is blocking process on the project or the IT servers is a blocker. Blocking is explicit in Bugzilla given that each bug can reference other bugs that are either dependent on its completion or the bug itself blocks another bug. A bug is not really complete unless all of the dependent bugs have been resolved.
 
Form: action or bug
== Communication Channel ==
Canmove, confirm, emeritus
2,305
edits

Navigation menu