Website Development Project: Sprint Start End Tasks
Website Development Project: Sprint Start End Tasks
1. Project Execution:
We will execute the project by breaking it down into smaller units, creating work breakdown structure
and planning for each task. We will create 3 sprints lasting 7 days.
2. Delivery model followed will be Structured Agile. This method combines both agile and waterfall
methodology. The first task is to understand the big picture and then break down into phases. Each
phase can be independent and run in parallel if their outputs don’t depend on each other, or they run
serially. Each sprint will have its own backlog and sub-modules.
1. Requirements Gathering: This phase will require discussions with the client on their
technical, user and functional requirements from the website. This will be articulated in
Business Requirements document, after noting down all requirements as well the KPIs to
measure them. Most importantly we need to know the end user of this website and keep it in
mind throughout the design.
2. Planning sitemap and wireframe creation: Sitemap is the relationship between different
pages on the website and helps in understanding the inner structure/links. Wireframe is the
rough sketch of User Interface (UI) that will be created. It specifies the elements that will be
added to the page and their location.
3. Design: The visual content is created in this step, is reviewed by customer and approved.
4. Content Writing: Catchy headings, text for each element is added in this step.
5. Coding (Build and Deploy): We finalize the technology stack to work on and start building
the sitemap from the home page. We insert all graphics and text as designed and also Search
Engine Optimization (SEO) is done so that the website ranks better in search results.
6. Testing and Review: The website is tested for all business requirements that were
documented. In addition, we check for
o Broken links
o Following current web standards
o Penetration testing against hacking
o SEO
o Load time (as promised <0.5 sec)
o Load testing
o Compatibility with different browsers
a. Assumptions:
We assume that
o The requirements for the next 5 modules will come within 10 days of project
initiation (including non-working days).
o The client will be free to help and approve the UI designs whenever required.
o Funding is sufficient to complete the project in the given time.
o Project team members will have the resources they need to complete their
individual tasks on time, from specialized equipment and software down to
electricity during working hours.
o Personnel costs will not change during the project cycle.
o Other material and resource costs will remain consistent throughout the project.
o The overall cost of day-to-day operations will not increase.
o All equipment will be in working condition through the project cycle.
o The scope of the project will not change throughout the life cycle
c. Effort estimation
Breaking the project into smallest tasks and taking into account each task:
1. Requirements Gathering: 1 day: Business Analyst
2. Planning sitemap & Wireframe creation
2.1 Planning sitemap: 1 day : Business Analyst + Developer
2.2 Wireframe creation : 1 day : UI designer
3. UI design: 1 days: UI designer
4. Content: 2 days: Content editor
5. Coding: 2 day: Developers
5.1 Build UI
5.2 Server side development
5.3 Special Features if required
5.4 Deploy (1day)
6. Testing : 2 days: QA Tester
6.1 Test on website itself
6.2 Test on server
6.3 UAT (1day)
d. Resource planning
In the Agile module, I have assumed that Business Analyst, QA Tester are performed by
Developer, hence we have 3 types of human resource: Developer, UI Designer, Content Editor.
We assume we have 7 of each resource type and each is working on one sub-module when they
are running in parallel.
MAN POWER S S M T W T F S S M T W T F S S M T W T F S
S M T W T F S S M
0 0 0 0 0 0 0 0 0 1 1 1 1 1 1 1 1 1 1 2 2 2
2 2 2 2 2 2 2 3 3
1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2
3 4 5 6 7 8 9 0 1
- - - - - - - - - - - - - - - - - - - - - -
- - - - - - - - -
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
0 0 0 0 0 0 0 0 0
Sr. No. 8 8 8 8 8 8 8 8 8 8 8 8 8 8 8 8 8 8 8 8 8 8
8 8 8 8 8 8 8 8 8
DESCRIPTION NO.S
- - - - - - - - - - - - - - - - - - - - - -
- - - - - - - - -
2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2
2 2 2 2 2 2 2 2 2
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
0 0 0 0 0 0 0 0 0
2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2
2 2 2 2 2 2 2 2 2
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
0 0 0 0 0 0 0 0 0
Sprint 1 Review Sprint 2 Sprint 3
1 Developer 1 1 RG PS Cod Cod QA UAT RG PS RG/PS Cod QA Cod Cod QA UAT RG PS Cod CodQA
2 Developer 2 1 RG PS Cod Cod QA UAT RG PS RG/PS Cod QA Cod Cod QA UAT RG PS Cod CodQA
3 Developer 3 1 RG PS Cod Cod QA UAT RG PS RG/PS Cod QA Cod Cod QA UAT RG PS Cod CodQA
4 Developer 4 1 RG PS Cod Cod QA UAT RG PS RG/PS Cod QA Cod Cod QA UAT RG PS Cod CodQA
5 Developer 5 1 RG PS Cod Cod QA UAT RG PS RG/PS Cod QA Cod Cod QA UAT RG PS Cod CodQA
6 Developer 6 1 RG PS Cod Cod QA UAT RG PS RG/PS Cod QA Cod Cod QA UAT RG PS Cod CodQA
7 Developer 7 1 RG PS Cod Cod QA UAT RG PS RG/PS Cod QA Cod Cod QA UAT RG PS Cod CodQA
8 UI Designer 1 1 WF
UI D WF WF UI D UI D WF UI D
9 UI Designer 2 1 WF
UI D WF WF UI D UI D WF UI D
10 UI Designer 3 1 WF
UI D WF WF UI D UI D WF UI D
11 UI Designer 4 1 WF
UI D WF WF UI D UI D WF UI D
12 UI Designer 5 1 WF
UI D WF WF UI D UI D WF UI D
13 UI Designer 6 1 WF
UI D WF WF UI D UI D WF UI D
14 UI Designer 7 1 WF
UI D WF WF UI D UI D WF UI D
15 Content Editor 1 1 Con Con Con Con Con Con ConCon
16 Content Editor 2 1 Con Con Con Con Con Con ConCon
17 Content Editor 3 1 Con Con Con Con Con Con ConCon
18 Content Editor 4 1 Con Con Con Con Con Con ConCon
19 Content Editor 5 1 Con Con Con Con Con Con ConCon
20 Content Editor 6 1 Con Con Con Con Con Con ConCon
21 Content Editor 7 1 Con Con Con Con Con Con ConCon
22 Project Manager 1 PM PM PM PM PM PM PM PM PM PM PM PM PM PM PM PM PM PM PM PM PM PM PM PM PM PM PM PM PM
Total 22
If we have different business analyst, developer and QA testing, then manpower planning looks
as shown below. This follows waterfall model where in each sprint we develop 5 modules and we
have fifth sprint to revisit the sub-modules of first and second sprints so that we can modify
anything that came up in the requirements later.
MAN POWER FTD Cumm. S S M T W T F S S M T W T F S S M T W T F S S M T W T F S S M
0 0 0 0 0 0 0 0 0 1 1 1 1 1 1 1 1 1 1 2 2 2 2 2 2 2 2 2 2 3 3
1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
Sr. No. 8 8 8 8 8 8 8 8 8 8 8 8 8 8 8 8 8 8 8 8 8 8 8 8 8 8 8 8 8 8 8
DESCRIPTION NO.S NO.S
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
1 Business Analyst 1 7 1*5(S1) 1*5 (S1) 1*5(S2) 1*5 (S2) 1*5(S3) 1*5(S3) 1*5(S4) 1*5(S4) 1*5(S5) 1*5(S4)
2 Developer 1 7 1*5 (S1) 1*5 (S2) 2*5 (S1) 1*5(S3) 2*5 (S2) 2*5(S4,S5) 2*5(S4,S5) 2*5 (S3) 2*5 (S4) 2*5(S5)
3 UI Designer 1 7 1*5(S1) 1*5 (S1) 1*5 (S1) 1*5(S2) 1*5 (S2) 1*5 (S2) 1*5 (S5) 1*5(S3) 1*5(S3) 1*5 (S3) 1*5(S4) 1*5(S4) 1*5 (S4) 1*5(S5) 1*5(S5)
4 Content Editor 1 7 1*5 (S1) 1*5 (S1) 1*5 (S2) 1*5 (S2) 1*5(S3) 1*5 (S3) 1*5(S4) 1*5 (S4) 1*5(S5)
5 QA Test 1 7 2*5 (S1) 2*5 (S1) 2*5 (S2) 2*5 (S2) 2*5 (S3) 2*5 (S3) 2*5 (S4) 2*5 (S4) 2*5(S5) 2*5(S5)
Sprint 1
Sprint 2
Sprint 3
Sprint 4
Sprint 5
6 Project manager 1 1
Total 36
f. Process to accommodate five new requirements that will arrive during the course of the project