Proc and Cons of Sequential
and Parallel
Sequential
• Pros
– Upfront planning provide reference
at any stage for project status.
– Resources known and managed
– Control through Chain of command
– Managed risks
– Formal Nature
– Lesser no of experts in Team
– Only pre agreed deployment.
– End Date estimation
• Other points change on
circumstances
– Minor Refactoring only
– Illusion of estimated approach
– Bureaucratic in nature
Parallel
• Pros
– Customer Driven
– Chaotic in nature
– Iterative confidence buildup
– Change agility
– Developer decision for design
– Ensured Quality and
– Business value game
– Collaborative Customer Relation
– Iterative development and deployment
– Testing is also iterative so can’t be squeezed
– Automated test suit is not time expensive
– Value of product becomes evident during
development a and closure of project does not
result in desperation for any party
• Other points change on
circumstances
– Autocratic in nature
– Good for small Teams
– Code that is sufficient rather than speculative
 Proc and Cons of Sequential
and Parallel
Sequential Parallel
• Cons • Cons
– Competitive customer relation – Trust based contracts
– More Resources
– Project may linger forever
• Human, Financial, Special, others
–
– Exhaustive for Team.
Nothing to show up till last stages
except huge bill. – Only experts constitute a team
– Exhaustive efforts on planning rather – Customer may get annoyed with
then product. constant involvement
– Long term planning yields larger
– Test Team is engaged from start
slippages.
–
to end
Easily converts to a roadblock and
raises desperation. – Complexity increases incase of
– Change is undesirable distributed teams
– Testing might gets squeezed due to – Loosing Site of big picture
slippages – Testing of expectations
– Only Quality could become variable in
large products
– No fallback in case of contingency (In
case of accident)
 Initiation
Sequential Parallel
• Team Formulation.
• Technical.
• Core Team Formation
• Support.
• List Modules
• Project Lead Identification.
• Organization. • List Support People
• Module identification.
• Project Plan. • Plan Requirements
• Define Operational Process. • Define Operational
• Decide Formats and standards.
• SCM System Process
– Plan,
– Design and • SCM System
– Implement – Plan,
• Prepare for next phase.
– Design and
– Implement
 Requirements
Sequential Parallel
• Analyze Requirements. • Analyze initial
• Remove any ambiguities.
requirements.
• Complete details.
• Gather general
• Prepare RDD.
• Get it approved from all parties.
understanding.
• Incorporate suggestions. • Prepare Backlog
• Finalize RDD.
• Future iteration
• Baseline. (functional or containing requirements
requirements baseline)
to be completed.
• Understanding is
developed to take on
Requirements.
 System Analysis
Sequential
• Suggest solutions for
requirements in RDD.
• Technical solutions.
• Financial solutions.
• Finalize Working
requirements.
• Performance.
• Reliability.
• Quality.
• Prototype (if required)
• Evolution or Throwaway.
• Tools used.
• Demonstrate for feed back.
• Prepare SAD.
• Usability plan for of the shelf
components.
Parallel
• Each member works on
task at hand and
analyze problem for a
solution.
• Analyze what to re-
factor or create.
•Requirements review is conducted on the
start of each Iteration.
•Testable Task specification against
requirements.
•Prioritize tasks.
•Estimate tasks.
•Allocate tasks.
•Create test scenarios. (may even write
test before development)

Sequential
• Establish design
objectives.
• Prepare HLD
• Prepare system
component list.
• UI design.
• Interfaces and modules up
to routine level.
• Reports.
• Navigation details.
• Help and error messages.
• Prepare STP and STS.
Design HighLevel
Parallel
• Each member works on task
at hand and design a
solution.
• High level design is
discussed in Requirements
review each time.
• Design how to re-factor or
create a skeleton.
•Requirements review is conducted on the
start of each Iteration.
•Testable Task specification against
requirements.
•Prioritize tasks.
•Estimate tasks.
•Allocate tasks.
•Create test scenarios. (may even write
test before development)

Sequential
• Finalize on what libraries
or routines are to be
used.
• Prepare LLD.
• Finalize Low level details.
• Prepare UTS and UTP.
• Refine and update
previously prepared and
controlled documents.
• Baseline (allocated or
design baseline)
Design LowLevel
Parallel
• Designing is repeated in
each iteration.
• Low level design is
developer’s
responsibility.
• Design unit tests.
•Requirements review is conducted on the
start of each Iteration.
•Testable Task specification against
requirements.
•Prioritize tasks.
•Estimate tasks.
•Allocate tasks.
•Create test scenarios. (may even write
test before development)
 Development and Unit test
Sequential
• Code program.
• Conduct unit testing.
• Implement help and
error messages.
• Update design
documents if required.
• Fix errors.
• Update defect log.
• Initiate corrective action.
• Record unit test results
and other data
generated in process.
Parallel
• Each member works on
task at hand and
implements a solution.
• Re-factor or create a
new implementation.
• Code unit test before or
after Implementation.
•Requirements review is conducted on the
start of each Iteration.
•Testable Task specification against
requirements.
•Prioritize tasks.
•Estimate tasks.
•Allocate tasks.
•Create test scenarios. (may even write
test before development)

Sequential
• STS and STP are used to
conduct Integrated tests
• alpha testing
– Limited users test integrated
system
• beta testing
– Full fledge testing
• Test results recording
• Diagnose and fix recorded
bugs
• Update defect logs
• Initiate corrective action
• Perform regression testing
• Baseline. (product baseline)
Integrated test.
Parallel
• Implemented solution is
finalized only if integrated
solution implements some
feature fulfilling (partial or
complete) requirement.
• Integrated testing is done
on the go for each new
feature implemented.
•Requirements review is conducted on the
start of each Iteration.
•Testable Task specification against
requirements.
•Prioritize tasks.
•Estimate tasks.
•Allocate tasks.
•Create test scenarios. (may even write
test before development)
 Acceptance test.
Sequential
• User acceptance.
• Conducted by
– Client or
– Authorized entity.
• Development team helps.
– Make work products available.
– Record Errors and fix them.
• Update defect logs.
• Initiate corrective action.
• Perform regression testing.
• Record results and highlight
disagreements.
Parallel
• Demonstrate product
delta to the customers
and team.
• Get Acceptance of
product delta.
• Get project clearance.
•Acceptance review is conducted at the end
of each Iteration.
•Test features against requirements
involving all involved parties.
•Get clearance from stakeholders.
•Get go ahead for release.
•Get go ahead for project.
•Process review is also conducted between
Acceptance and Requirements Review.
 Implement
Sequential Parallel
• Development team • System deployment is
supervises the planed.
installation. • Core team (member)
• Maintenance team provides assistance in
takes over. – deployment.
– Enhancements. – Maintenance.
– Technical support.
– Bugs recording and
fixing.
 Wind up
Sequential Parallel
• Project ending • Proceed as planned
appraisals. during deployment.
• Release resources • Free all resources
excluding related to except related to
support. support.
• Return client property.
• Ensure complete
documentation is
retained in proper NOTE: This phase is a
format. part of deployment
plan and not executed
separately.
 Maintenance
Sequential Parallel
• True benefits of SCM • Maintenance may or
could be picked in this may not be provided
phase. by development team
– All the support so this is also done in
documentation is the same way as
available in this phase iterations during
for maintenance.
development is done.
– Easy bug fixing during
this phase. These Iterations may be
planned by the core
team during execution
of other projects as
well.
 Retirement
Sequential Parallel
• SCM resources are • Reasons may be
released. Unavailability of Core
• Maintenance team team (members).
disbands. • Same as sequential
• Reasons may be process’s same phase.
ineffectiveness of
– Cost.
– Resources.
• Requirements of
resources for some
other projects.
 Project Phases Outputs
Project Phase Documents in Controlled Documents SCM Documents
preparation

Initiation RDD Project Plan, Standards and SCM Plan Meeting

guide Lines Minutes ,
Policies,
Requirement RDD CR and
Rules and
Analysis and PRs for
Regulations.
Specification controlled
Organization
Document
System Analysis HLD SAD, Usability plan structures,
s, CR and
Standard
High Level Design LLD, user HLD, STP, STS PR Status
Forms and
documents Reports
manuals,
Low Level Design user documentsLLD, UTS, UTP Process and
procedures ,
Version
Coding and Unit user documentsUnit tested Programs, Test
Reports,
testing Data
CI Status
System Testing user documentsTest Data Tested Programs Reports

Acceptance Testing Test Results Reports,

Accepted and Rejected
feature lists, user SCM
Reposito
documents ry
Implementation FAQs