This presentation is divided into two parts: Part I looks into PRINCE2 and Agile methodologies and how they can be successfully integrated; Part II defines the pillars of software quality and discusses different methods to deliver it.

1. Presentation by
Sanjay Kaler

2. Part I
PRINCE2 + AGILE = SUCCESS

3. PRINCE2
• Macro-level control and stability

4. PRINCE2 Benefits
• Business case driven
• Stakeholder engagement
• Defined roles and responsibilities
• Manage by stages: start, middle and end
• Manage by exception and tolerance
• Product-based planning
• Work packages
• Change control
• Mechanism to confirm benefits
• Learn from experience

5. PRINCE2 Framework

6. Agile
• Micro-level agility and control
• Scrum is the dominant Agile approach with up
to 66% adoption rate

7. Agile Benefits
• Focus on business needs
• Respond to change over following a plan
• Cross-functional and self-organising team
• Collaborate
• Never compromise quality
• Build incrementally from firm foundations
• Develop iteratively
• Time boxed
• Communicate continuously and clearly
• Demonstrate control

8. Scrum Framework

9. Integrate
Use PRINCE2 for Project Management
Use Agile for Product Delivery

10. Process Coverage

11. Project Organisation

12. Rethink: Change
• PRINCE2: shouldn’t be the rule, must be
tightly controlled
• Agile: happens always, we deal with it
anyways

13. Rethink: Scope
• PRINCE2: we can accurately predict what we
need and what will happen
• Agile: we work with business to capture as
much value as possible in a given time and
budget

14. Rethink: Learning
• PRINCE2: learning is captured at the end of
project
• Agile: learning happens throughout the
project

15. Change Mindset
• Refocus risk management from cost containment to
value lost
• Management by exception: focus on Time & Cost vs.
focus on Scope
• Senior User & Project Manager/Team Manager vs.
Product Owner & Scrum Master
• Think requirements vs. Product features
• Reduce level of detail in planning products
• Rethink quality approach
• Lessons learned happens during and after every time
box

16. Part II
PILLARS OF QUALITY SOFTWARE
DELIVERY

17. Definition of Software Quality
In the context of software
engineering, software quality measures how
well software is designed (quality of
design), and how well the software conforms
to that design (quality of conformance). It is
often described as the 'fitness for purpose' of
a piece of software.

18. Functional Quality
• Meeting the specified
requirements
• Creating software that
has few defects
• Good enough
performance
• Ease of learning and
ease of use

19. Structural Quality
• Code understandability
• Code maintainability
• Code testability
• Code efficiency
• Code security

20. Process Quality
• Meeting delivery dates
• Meeting budgets
• A repeatable development process that reliably
delivers quality software

21. Establish Balance
• Different stakeholders: users, development
teams and sponsors, have different priorities
for quality
• Providing equal emphasis on functional,
structural and process quality allows to
include interests of all three stakeholders
• Quality measurement tools should be tailored
to project requirements and user needs

22. HOW TO ACHIEVE SOFTWARE
QUALITY OBJECTIVE

23. Process
• Pair programming or at a minimum peer review
• Test-driven development
• Define coding standards and enforce them
• Get customer actively involved during the
development
• Allocate time to pay down technical debt
• Track the source of defects that make it through
• Automate regression testing

24. People
• Right attitude in people and teams
• Motivate and move the team around for
valued experience and skill
• Encourage processes that allow individuals
and teams to share experiences and lessons
learnt
• Strategise around technologies and tools
• Good training support

25. Project Management
• Guide not control
• Continuous learning
• Tailor to suite business needs
• Align user requirements with business
objectives and team goals