synapseindia reviews on redesigning software development processes part 1
DESCRIPTION
SynapseIndia Reviews on Redesigning Software Development Processes Part 1SynapseIndia Employee Complaints,SynapseIndia Employee Reviews,SynapseIndia Court Cases,SynapseIndia Employee Feedback,SynapseIndia Employee Bond,SynapseIndia Abuse Employee,SynapseIndia Employee HarassmentTRANSCRIPT
1
SynapseIndia Reviews on Redesigning Software Development
Processes Part 1
Recurring problems
2
What is the best way to organize software development project?
How to speed up development, reduce costs and improve software quality?
How to achieve the quickest development effort, lowest effective development cost, and best available product quality?
Possible solutions
3
Attain and improve maturity of software development capabilities (image)
Get best people to practice standards-based development process supported by IDEs
(Re)Design your software production architecture (SPA) to optimize use of development resources, processes, and people.
Goals
4
Present an approach for how to optimize software production
Identify key concepts, techniques, and tools that enable better optimization
Describe optimization transformations from business process redesign studies
Describe opportunity areas for exploitation and use
Definitions and Differences
5
Software production: enterprise processes and resources that produce software
Production strategies: business strategies guiding overall approach to building software
Production architecture: configuration of enterprise capabilities to enact strategies
Optimizing production: minimizing enterprise configuration to maximize strategic options
(Re)designing software production
6
What first: to-be goal vs. as-is mess?If you don’t know where you are, any road will
do (proverb)Observation: people at work cannot describe
the processes they do with high fidelity (tacit knowledge)
Redesign necessitates understanding as-is, to-be, and here-to-there
Creating high-performance work groupsEmpowerment, participation, incentivization
(resource sovereignty), and recognition
Software Production Strategies
7
Reduce costsReduce cycle time Improve cash flowCustomer
satisfactionIncrease salesImprove customer
service
Increase productivity
Open new marketsOpen new
“channels”Be innovation
leaderIncrease market
shareEnable just-in-time
service delivery
Software Production Architecture
8
A composite model that interrelatessoftware system architecturesoftware process architecturedevelopment organization architecturenetwork infrastructure and development
tools/environment configuration documentation architecturecustomer-support knowledge base
architecture
Optimizing Software Production
9
Strategies provide global constraints or opportunities for optimizing software production
Constraints and opportunities realized in software production enterprise
Constraints and opportunities are distributed across the software production architecture
Optimizing Software Production
10
Optimization must address composite architecture of software production
Local optimization of any component architecture does not guarantee global optimality of software production
Diagnostic analyses and transformation heuristics applied to composite architectural models lead to optimization opportunities
Optimizing Software Production
11
Transformation heuristics classified taxonomically
Taxonomy classifies domain-independent and domain-specific hueristics
DI transformations applied in any software production setting
DS transformations applied to specific component architectures
Optimizing Software Production
12
DI transformation classes (sample):Job scopeWorker empowermentOrganization designWorkflow streamliningInformation technology (IT)
Research grant justification and approval process at Office of Naval Research (c. 1995)
13
Optimizing Software Production
14
IT transformation sub-classes (sample):Extend IT-based support to manual process
steps Extend IT-based communication facilities to
encourage information sharing activities Extend IT-based automation to incorporate
new kinds of application packages Extend IT-based integration to interconnect
and interrelate existing "islands of automation"
15
As-is vs. to-be process
16