Making IT clear.High quality independent analysis of
a business concept, from feasibility and business case, to
translation into IT architecture, lifecycle roadmaps,
structured requirements - to allow high quality testing,
detailed specifications, and overall solution
design.
This is a crucial phase, not one you would want
skipped or looked over too easily!
IT Projects can be
complex in content; there is no need for further obfuscation
in form.
“Analysis by S3M - the way it should be
done. No monkey business!”
Luc Pluys
ICT Manager
of the Year 2009
Van Genechten Packaging
S3M proposes a no-nonsense approach to
Analysis work.
No monkey business!
 |
 |
 An idea sprouts from
business oriented people, commercial and marketing
departments, and is then handed to technical teams to provide
the technological solutions supporting that business case.
How will the solution be realized? How should it look?
What should it integrate with? How long is it expected to
live? Will it be extended along the way? How will new
functionality affect existing systems?
There are
hundreds of questions, business users never thought existed,
and technical teams don’t assume are left unanswered.
 This is where the
analysts come in, and to maximize clarity of vision, handovers
are minimized in our approach.
There really is hardly
ever a need for dedicated business analysts, who then hand
over their findings to functional analysts, who then transfer
their output to technical designers and architects.
End-to-end
analysts are best positioned to have end-to-end oversight, and
keep things under control. In ModularS3M™, analysts set out
the lines within which the solution is to function, and then
focus on regular delivery of modular information pieces which
are fitting into the future solution. Designers, developers,
analysts and testers will be working on the same elements in
parallel, enabling modular delivery, earlier feedback, and
maximized return on human capital investments. |
|
The analysts
of S3M apply the Unified Process and best practices of
software engineering.
Develop Iteratively
Manage Requirements
Use Component Architectures
Model Visually
Continuously Verify Quality
Strengths of the Unified Process:
Provides a common lexicon for all workers on a project
Increases project outcome predictability
Reduces project risk
Weaknesses of the Unified
Process:
Many disciplines, roles, tasks and artifacts
Implementing all of the Unified Process may take years
What do we implement first?
While we fully build on the strengths, we
counter the weaknesses by:
Working with a reduced set of roles and artifacts,
adhering to agile principles
Only applying process implementation there where it is
needed (no blanket approach)
Through the output driven approach of ModularS3M™, our
analysts and project managers can rely on integrated best
practices from the start and expertise at their disposal
through our Competence Centers.
|
