Application Development

Practices
Nguyen Tran Hoang Linh
Instructor of DTU

Using Processes

© 2021, Nguyen Tran Hoang Linh 1

Previous lesson
 The team is build in…?
 TRUST

 What is “A results-driven structure”

characteristic?
 Roles & Accountabilities
 Communication
 Monitoring individual performance
& providing feedback

Referenced from Prof.Redley of CMU © 2021, Nguyen Tran Hoang Linh 2

Previous lesson
 Two ways of team member
competencies are?
 Technical
 Personal
 Characteristics of good team leader?
 A consistent message
 Unleashing talent
 A decision making climate
 Ego suppression
 Leaders create leaders

Referenced from Prof.Redley of CMU © 2021, Nguyen Tran Hoang Linh 3

Agenda
 Why Process is Important
 What is a Process?
 What Processes Will I Need?

Referenced from Prof.Redley of CMU © 2021, Nguyen Tran Hoang Linh 4

Why Process is Important
 What has the biggest impact on
project success and quality?

 What processes, standards &

conventions will your team need to be
successful?
Referenced from Prof.Redley of CMU © 2021, Nguyen Tran Hoang Linh 5
What is a Process?
 A process is a set of practices
performed to achieve a given purpose;
it may include tools, methods,
materials, and/or people
 While process is often described as a
leg of the process-people-technology
triad, it may also be considered the
“glue” that unifies the other aspects

Referenced from Prof.Redley of CMU © 2021, Nguyen Tran Hoang Linh 6

Why Focus on Process?
 Everyone realizes
the importance of
having a
motivated, quality
work force, but
even our finest
people can’t
perform at their
best when the
process is not
understood or
operating “at its
best”

Referenced from Prof.Redley of CMU © 2021, Nguyen Tran Hoang Linh 7

Ví dụ 1

Referenced from Prof.Redley of CMU © 2021, Nguyen Tran Hoang Linh 8

Ví dụ 2
 http://vhr.vn/quy-trinh-giao-dich-vinhomes-riverside-hoa-anh-dao.html

Referenced from Prof.Redley of CMU © 2021, Nguyen Tran Hoang Linh 9

Ví dụ 3

Referenced from Prof.Redley of CMU © 2021, Nguyen Tran Hoang Linh 10

Process Improvement Premise
 “The quality of a product is largely
determined by the quality of the process
that is used to develop and maintain it.”
- Based on Total Quality Management
principles as taught by Shewhart, Juran,
Deming and Humphrey

Referenced from Prof.Redley of CMU © 2021, Nguyen Tran Hoang Linh 11

How Do We Define a Process?
 Processes do or transform something

 Two Examples in Readings:

 ETVX
 Swim Lane

Referenced from Prof.Redley of CMU © 2021, Nguyen Tran Hoang Linh 12

Process Measures
 You can specify where the process
measurements should be taken

Referenced from Prof.Redley of CMU © 2021, Nguyen Tran Hoang Linh 13

Black & White Box
 Black Box: You can’t see into the process

 White Box: You can see into the process

Referenced from Prof.Redley of CMU © 2021, Nguyen Tran Hoang Linh 14

Entry, Tasks, Validation, eXit

Referenced from Prof.Redley of CMU © 2021, Nguyen Tran Hoang Linh 15

Entry, Tasks, Validation, eXit

Referenced from Prof.Redley of CMU © 2021, Nguyen Tran Hoang Linh 16

Entry, Tasks, Validation, eXit

Referenced from Prof.Redley of CMU © 2021, Nguyen Tran Hoang Linh 17

Entry, Tasks, Validation, eXit

Referenced from Prof.Redley of CMU © 2021, Nguyen Tran Hoang Linh 18

Controls and Constraints

Referenced from Prof.Redley of CMU © 2021, Nguyen Tran Hoang Linh 19

Controls and Constraints
 Controls
 Designed into the process to produce
adesirable outcome. Examples:
 Policies
 Error detection and correction processes
 Constraints
 A limitation to the process (or
environment) that may impact process
effectiveness and/or efficiency. Examples:
 Technical capabilities of team
 Available time or resources
 Transmission speeds
Referenced from Prof.Redley of CMU © 2021, Nguyen Tran Hoang Linh 20
Swim Lane Diagram

Referenced from Prof.Redley of CMU © 2021, Nguyen Tran Hoang Linh 21

Development Processes
 Product requirements
 Top level architecture, technical
approach, and system design
 Component and unit specifications and
design
 Coding
 Unit and integration testing
 Implementing product changes
 Development metrics definition, collection
& analysis
Referenced from Prof.Redley of CMU © 2021, Nguyen Tran Hoang Linh 22
Infrastructure Processes
 Source control
 Configuration management
 Continuous integration
 Change control
 Infrastructure metrics definition,
collection & analysis
 Defect tracking

Referenced from Prof.Redley of CMU © 2021, Nguyen Tran Hoang Linh 23

Project Management Processes
 You’ll also need to consider processes
for:
 Project charter and business case
 Project planning
 Project scheduling
 Project budgeting
 Project and Program metrics definition,
collection and analysis
 Project tracking
 Project reporting
 Project control
Referenced from Prof.Redley of CMU © 2021, Nguyen Tran Hoang Linh 24
Quality Processes
 Quality planning
 Quality assurance (Defect Prevention)
 Quality metrics definition, collection
and analysis
 System testing
 Usability testing
 Performance testing
 Regression testing
 Inspections
Referenced from Prof.Redley of CMU © 2021, Nguyen Tran Hoang Linh 25
Support Processes
 System packaging and delivery
 User documentation & training
 User support
 Product returns
 Problem logging and initial triage
 System upgrades and routine software
maintenance
 Support metrics definition, collection
and analysis
Referenced from Prof.Redley of CMU © 2021, Nguyen Tran Hoang Linh 26
Along with Process ...
 Deliverables (Artifacts): The output of each
process. Some deliverables are for internal use
only, while others are packaged with the product
 Standards: The rules by which a process is
implemented. Standard electrical plug in
countries, for example
 Policies: An order, typically from senior
management, describing expected behavior by
employees
 Roles & Responsibilities: Who is responsible for
what and when
 Measurement definition, collection and analysis

Referenced from Prof.Redley of CMU © 2021, Nguyen Tran Hoang Linh 27

How Much Process Is Right?
 Whatever works for your team!
 Optimal, yet minimal
 More process is not necessarily better
 Each process must be an enabler for
the team
 If it isn’t, change the process until it is
 Each team member must buy in to
each process
 If they don’t, find out why and fix it

Referenced from Prof.Redley of CMU © 2021, Nguyen Tran Hoang Linh 28

How Much Process When?
 Start with:
 Basic Planning
 What does done, quality and success look like?
 Change Management
 Configuration Management
 Quality
 Defect tracking
 Testing

 Better:
 Add Continuous Integration
 Best:
 Use methodology pieces that work for you

Referenced from Prof.Redley of CMU © 2021, Nguyen Tran Hoang Linh 29

Tools
 Most of the software development
processes can be automated
 Many of the available software
development tools are free (open
source)
 Make sure that any tools you acquire
integrate well with existing or planned
processes

Referenced from Prof.Redley of CMU © 2021, Nguyen Tran Hoang Linh 30

Methodologies
 The documented collection of policies and
processes used by a development team
or organization to practice software
engineering is called its software
development methodology (SDM) or
system development life cycle (SDLC)
 You can use a defined methodology to
avoid having to define your own
processes
 Traditional
 Agile

Referenced from Prof.Redley of CMU © 2021, Nguyen Tran Hoang Linh 31

Example Change Request Process

Referenced from Prof.Redley of CMU © 2021, Nguyen Tran Hoang Linh 32

Example Process
 Change Request (CR) State Diagram

Referenced from Prof.Redley of CMU © 2021, Nguyen Tran Hoang Linh 33

Summary
 You will need some amount of process
as soon as you are no longer working
alone
 Methodologies can reduce the time
needed to build an agreed upon set of
processes for the team to use
 Change a process if it isn’t working for
your team

Referenced from Prof.Redley of CMU © 2021, Nguyen Tran Hoang Linh 34