Predictive Software Engineering Methodology

  • Predictive Software Engineering (PSE) is a framework that addresses bottlenecks of custom software product development. It reconstructs the reliable approach to delivering software development services.
  • PSE overcomes the “art” component of programming. It makes software engineering exactly what it was meant to be: an engineering exercise that is precise and predictable.

The PSE framework consists of seven specific concepts. Together they ensure transparency, as well as render the process controllable and predictable in its essence. PSE is a proprietary framework developed by Intetics as result of 25+ years in custom development practices.

01 Meaningful Customer Care 03 Proven Productivity 05 Disciplined Agile Delivery process 07 Sound Human Development
predictive_software
02 Transparent End-to-End Control 04 Efficient Distributed Teams 06 Measurable Quality Management and Technical Debt Reduction

title icon 01. Meaningful Customer Care

  • Seamless onboarding process

  • Customer portal

  • Governance model:

    • Weekly status meeting with manager
    • Every other week with director
    • Yearly with C-level
    • On site visits
  • Clear escalation path

  • Early problems discovery

    • Proactive project monitor
    • Project health report
  • Deep customer complain analysis

  • Customer satisfaction control

title icon 02. Transparent End-to-End Control

  • Transparency in organization – Intetics is quite transparent

  • Transparency outside:

    • Governance meetings
    • Agile methodologies
    • Status reporting
    • Tools to track team work
    • Audits: project health and proactive monitor
    • Video if required, security
    • TETRA
  • Transparency inside:

    • Meetings with C-level
    • Sync with directors and department
    • Sync with team and manager
    • HR involvement in team\engineer life
    • Team buildings corporate events

title icon 03. Proven Productivity

  • Productivity measurement: productivity = size/effort
    doesn’t address customer risk

  • Productivity promotion inside company – develop people skills

  • Productivity implementation:

    • Centers of excellence
    • Benchmarking
    • Project audits
    • TETRA
    • Success advertisement
  • Quality and velocity measurement:

    • TETRA
    • Software development efficiency KPIs
      • Team KPIs
      • Individual KPIs

title icon 04. Efficient Distributed Teams

  • Usual complains and risks about distributed teams:

    • Communication is not good as in collocated teams
    • Quiet participants and sense of being an island
    • Physical distance and different time zone
    • Socio-cultural difference
  • Forming distributed team:

    • Hiring to distributed team
    • Communication solution for distributed team
    • Leadership for distributed team
    • Rewarding and protecting distributed team
  • Benefits from distributed team:

    • Faster and efficient hiring
    • Price
    • More order
    • Best match
    • 24/7 Operation
    • More freedom
    • Learning about world
    • Office cost

title icon 05. Disciplined Agile Delivery Process

  • Standard Agile processes have challenges when you scale them

  • People invited new processes:

    • SAFE – Scaled Agile Framework
    • DAD – Disciplined Agile Delivery
    • LeSS – Large Scale Scrum
    • Etc.
  • We decided to go with DAD and that’s why:

    • Very flexible, tailoring supported
    • Focus on architecture and design
    • Proven, well documented and flexible
    • Clear roles, artifacts and event, medium complexity

title icon 06. Measurable Quality Management and Technical Debt Reduction

  • Quality is open question for each project, how to measure it
  • We use more wide and efficient term for quality: “technical debt”
  • TETRA is “Technical Debt Reduction Platform”
  • Eight dimensions of software product technical debt:

TETRA™
8 Dimensions
of Quality

scheme-tetra-2
SOURCE CODE QUALITY
USABILITY, UI & DOCUMENTATION
SECURITY
PERFORMANCE
BUSINESS LOGIC
ARCHITECTURE QUALITY
DATA QUALITY
OPEN SOURCE
CODE USE
  • Source Code Quality – assessment of quality of product source code by a number of critical parameters
  • Usability, UI & Documentation – evaluation of product user interface, usability and documentation
  • Security – valuation of product vulnerabilities according to CVE, CERT, CWE, OSVDB, OWASP, and BID
  • Performance – measurement of product performance and load parameters
  • Business Logic – audit of how product fits in to business objectives
  • Architecture Quality – expert assessment of product software core structure and data model
  • Data Quality – check of product resistance to bad data, exception handling, and bad data prevention
  • Open Source Code Use – detection of use of open source and other 3rd party code

title icon 07. Sound Human Development

  • Software development is 100% people dependent area of business

  • We must develop our people and we do following:

    • Career growth and attestation:

      • Individual development plan
      • Proprietary performance review system
      • Regular reviews
    • Skills improvement:

      • External advice
      • Training
      • Centers of excellence
    • Employee benefits:

      • Training and certification
      • Benefits package
      • English courses
      • Award winning work environment
    • Mentors program

PSE: Addressing main software engineering risks

PSE PRINCIPLES/
SOFTWARE ENGINEERING RISKS
I
Meaningful Customer Care
II
Transparent End-to-End Control
III
Proven Productivity
IV
Efficient Distributed Teams
V
Disciplined Agile Delivery process
VI
Measurable Quality Management and Technical Debt Reduction
VII
Sound Human Development
You don't receive the software product
Missed schedules
You spend more resources than needed
Lack of required resourses in time
Personnel knowledge (software + business)
Poor knowledge retention (high attrition)

PSE: Addressing main software engineering risks

PSE PRINCIPLES/
SOFTWARE ENGINEERING RISKS
I
Meaningful Customer Care
II
Transparent End-to-End Control
III
Proven Productivity
IV
Efficient Distributed Teams
V
Disciplined Agile Delivery process
VI
Measurable Quality Management and Technical Debt Reduction
VII
Sound Human Development
The received software product is not what you wanted
The received software product shows problems in use
Communication/cultural barriers
Poor infrastructure and processes
Service quality declines over time
Concerns about intellectual property security and legal framework

PREDICTIVE
SOFTWARE
ENGINEERING

Created by Global Engineering Community

How the Framework
Transforms Custom Software Products
Development and Services Into Radically
Successful Business Solutions

pse_abstract_star

Join PSE community
and become the ambassador!

pse_global_engineering_community