deletions | additions       diff --git a/WorkScopeAndPlan.md b/WorkScopeAndPlan.md  index 6ff4629..9e10ee5 100644  --- a/WorkScopeAndPlan.md  +++ b/WorkScopeAndPlan.md 
...
# Implementation Methodology Scope and Plan  ## Scope of work  The implementation methodology was based on some agile process concepts. As At  the development team was composed by only one person, several formal aspect beginning of the course we defined the initial scope  of the development process work and it  was ignored. divided in four main milestones:  ## Working Plan 1. Implement Composition Operators  1. Implement Tailoring Operators  1. Implement the generation of a BPMNt file  1. Integrate the operators with a web application    ### Implement Composition Operators  This milestone was the development of an API that offers some Processes Composition Operators for BPMN. The operators selected will be described at section ???.  We divided the work in unit of work known as 'Sprints'. Each sprint had the duration of 2 weeks (the exact interval between the presential classes). The sprints were organized as described in the plan below: ### Implement Tailoring Operators  * Sprint 1: Implement Composition Operators  * Sprint 2: Implement This milestone was similar with the last one but the focus was the development of some Process  Tailoring Operators (Basic and High Level)  * Sprint 3: for BPMN. The operators selected will be described in more details at the section ???.  ###  Implement the generation of a BPMNt file * Sprint 4: The goal of this task was the development an API that support the generation of a BPMNt file. The BPMNt file is described at section ????.   ###  Integrate the operators with a web application  The last task was integrating  the operators developed at milestones 1, 2 and 3 with a  web application module called ProcessHub-web. The goal was to validate the use of the API in a more real scenario. The ProcessHub-WebApp will be described at section ????.  The Figure ??? show this plan in a Gantt Project Graph.  ## Plan of Work   We divided the development in unit of work known as 'Sprints'. Each sprint had well defined milestone (delivery product) and the duration of 2 weeks (the interval between the classroom lessons). The sprints and milestones were organized as described in the plan below:  * Sprint 1: Implement Composition Operators (estimated end date: 7/24/15)  * Sprint 2: Implement Basic and High Level Tailoring Operators (estimated end date: 8/7/15)  * Sprint 3: Implement the generation of a BPMNt file (estimated end date: 8/21/15)  * Sprint 4: Integrate the operators with the web application module (estimated end date: 9/4/15)  The Figure ??? show this plan in a Gantt Project Graph.