Understanding the who, what, why, and when of quality is essential in implementing an effective Quality Program. It requires a combination of distinct disciplines: Quality Assurance, Quality Control, and Quality Improvement. They are three unique disciplines which, when used together, can improve the efficiency and effectiveness of any organization leading to reduced cost and increased customer satisfaction.
A case study on how applied Six Sigma principles led to increased efficiency and overall improvement in decreasing cycle-time in Protocol Development and Clinical Study Start-Up.
In this presentation that I delivered for a PMI-SOC event on May 21, 2015, I discuss how CMMI-DEV complements PMBOK in building mature Project Management processes. You will also find a brief discussion of how CMMI and OPM3 differs in in their approach as well as what commonalities they have. Hope you enjoy !
Understanding the who, what, why, and when of quality is essential in implementing an effective Quality Program. It requires a combination of distinct disciplines: Quality Assurance, Quality Control, and Quality Improvement. They are three unique disciplines which, when used together, can improve the efficiency and effectiveness of any organization leading to reduced cost and increased customer satisfaction.
A case study on how applied Six Sigma principles led to increased efficiency and overall improvement in decreasing cycle-time in Protocol Development and Clinical Study Start-Up.
In this presentation that I delivered for a PMI-SOC event on May 21, 2015, I discuss how CMMI-DEV complements PMBOK in building mature Project Management processes. You will also find a brief discussion of how CMMI and OPM3 differs in in their approach as well as what commonalities they have. Hope you enjoy !
This presentation has been compiled using material available in public domain. Copyrights of the owners and sources of the material used has been duly acknowledged.
Episode 24 : Project Quality Management
Include the processes required to ensure that the project will satisfy the needs for which it was undertaken
Include all activities of the overall management function that determine the quality policy, objectives and responsibilities and implements them by means such as quality planning, quality assurance, quality control, and quality improvement, within the quality system
The presentation discuss in detail the Project Quality Management in light of PMI PMBOK prospective. After highlighting the basic concepts from PMBOK initial chapter, it captures the details from all the processes of PQM, mainly Plan Quality Management, Perform Quality Assurance and Control Quality. The presentation also includes some of the sample questions related to Project Quality Management.
20210113 Lean In Government Harrisburg Conf Agile Governance at Scale Craeg S...Craeg Strong
Traditional duties of IT governance and oversight include auditing timely completion of milestones and phase gates and tracking progress versus spend. They place heavy emphasis on correctness and completeness of documentation, managing risks and tracking metrics such as earned value and escaped defect counts. With the adoption of agile methods comes the need to adjust governance and oversight accordingly. But what does agile governance look like? How does it differ from traditional governance? Given the lack of detailed plans up-front, the reduced emphasis on documentation, and the eschewing of traditional metrics such as earned value, one might assume that governance and oversight is more challenging in the agile space. Looking at governance and oversight through a traditional lens reveals relatively few effective tools and the necessity of relying upon vaguely defined metrics such as “story points.” However, we will show that, in fact, agile methods offer governance and oversight a wealth of new tools and capabilities, enabling a more proactive and collaborative approach—which could ultimately lead to improved outcomes.
Product audits have been an indispensable tool in the automotive industry for evaluating and improving product quality in the interest of the customers for many years.
CMMI 2.0 deployment case study document gives an overview of the rapid deployment achieved at a proactive client site with handful of initiatives to demonstrate true and sustained improvements in the processes. The fact that benchmark assessment was successful with very few changes identified on the Assessment Team Members.
Taking Back Your Manufacturing Plant Through Continuous Improvement Frank Donohue
Find out why Six Sigma, Lean Sigma, and Continuous Improvement initiatives didn't always live up to the hype in the past, and how you can start a Continuous Improvement Program that has teeth and will get your organization tangible results.
Accelerating Business Growth with Agile Software Delivery.pdfSeasia Infotech
The customary approaches for software development have divided development and testing into two diverse steps- developers build a feature and the QA team tests it for defects.
DevOps is a term for a combination of various software development practices including traditional software development and information technology operations. It shortens the systems development life cycle while delivering features, fixes, and updates. This is ensured by frequent and close alignments with business objectives. It comprises a vast set of cultural philosophies, practices and tools
to increase an organization's ability to deliver applications and services at high velocity.
This document gives insights how DevOps should be designed, what services they should offer, what organizational forms can be chosen (incl. their benefits), which aspects a DevOps governance should cover, how to assess and implement DevOps (DevOps transition), which technologies are important and how processes can be designed based on proven best practices.
Agenda DevOps best practice slide deck:
- DevOps Definition and Overview
- DevOps & Agile maturity
- DevOps Transition
- DevOps Technology
- DevOps Organization
This presentation has been compiled using material available in public domain. Copyrights of the owners and sources of the material used has been duly acknowledged.
Episode 24 : Project Quality Management
Include the processes required to ensure that the project will satisfy the needs for which it was undertaken
Include all activities of the overall management function that determine the quality policy, objectives and responsibilities and implements them by means such as quality planning, quality assurance, quality control, and quality improvement, within the quality system
The presentation discuss in detail the Project Quality Management in light of PMI PMBOK prospective. After highlighting the basic concepts from PMBOK initial chapter, it captures the details from all the processes of PQM, mainly Plan Quality Management, Perform Quality Assurance and Control Quality. The presentation also includes some of the sample questions related to Project Quality Management.
20210113 Lean In Government Harrisburg Conf Agile Governance at Scale Craeg S...Craeg Strong
Traditional duties of IT governance and oversight include auditing timely completion of milestones and phase gates and tracking progress versus spend. They place heavy emphasis on correctness and completeness of documentation, managing risks and tracking metrics such as earned value and escaped defect counts. With the adoption of agile methods comes the need to adjust governance and oversight accordingly. But what does agile governance look like? How does it differ from traditional governance? Given the lack of detailed plans up-front, the reduced emphasis on documentation, and the eschewing of traditional metrics such as earned value, one might assume that governance and oversight is more challenging in the agile space. Looking at governance and oversight through a traditional lens reveals relatively few effective tools and the necessity of relying upon vaguely defined metrics such as “story points.” However, we will show that, in fact, agile methods offer governance and oversight a wealth of new tools and capabilities, enabling a more proactive and collaborative approach—which could ultimately lead to improved outcomes.
Product audits have been an indispensable tool in the automotive industry for evaluating and improving product quality in the interest of the customers for many years.
CMMI 2.0 deployment case study document gives an overview of the rapid deployment achieved at a proactive client site with handful of initiatives to demonstrate true and sustained improvements in the processes. The fact that benchmark assessment was successful with very few changes identified on the Assessment Team Members.
Taking Back Your Manufacturing Plant Through Continuous Improvement Frank Donohue
Find out why Six Sigma, Lean Sigma, and Continuous Improvement initiatives didn't always live up to the hype in the past, and how you can start a Continuous Improvement Program that has teeth and will get your organization tangible results.
Accelerating Business Growth with Agile Software Delivery.pdfSeasia Infotech
The customary approaches for software development have divided development and testing into two diverse steps- developers build a feature and the QA team tests it for defects.
DevOps is a term for a combination of various software development practices including traditional software development and information technology operations. It shortens the systems development life cycle while delivering features, fixes, and updates. This is ensured by frequent and close alignments with business objectives. It comprises a vast set of cultural philosophies, practices and tools
to increase an organization's ability to deliver applications and services at high velocity.
This document gives insights how DevOps should be designed, what services they should offer, what organizational forms can be chosen (incl. their benefits), which aspects a DevOps governance should cover, how to assess and implement DevOps (DevOps transition), which technologies are important and how processes can be designed based on proven best practices.
Agenda DevOps best practice slide deck:
- DevOps Definition and Overview
- DevOps & Agile maturity
- DevOps Transition
- DevOps Technology
- DevOps Organization
Your Challenge
Companies are approving more projects than they can deliver. Most organizations say they have too many projects on the go and an unmanageable and ever-growing backlog of things to get to.
While organizations want to achieve a high throughput of approved projects, many are unable or unwilling to allocate an appropriate level of IT resourcing to adequately match the number of approved initiatives.
Portfolio management practices must find a way to accommodate stakeholder needs without sacrificing the portfolio to low-value initiatives that do not align with business goals.
Our Advice
Critical Insight
Failure to align projects with strategic goals and resource capacity are the most common causes of portfolio waste across organizations. Intake, approval, and prioritization represent the best opportunities to ensure this alignment.
More time spent with stakeholders during the ideation phase to help set realistic expectations for stakeholders and enhance visibility into IT’s capacity and processes is key to both project and organizational success.
Too much intake red tape will lead to an underground economy of projects that escape portfolio oversight, while too little intake formality will lead to a wild west of approvals that could overwhelm the PMO. Finding the right balance of intake formality for your organization is the key to establishing a PMO that has the ability to focus on the right things.
Impact and Result
Eliminate off-the-grid initiatives by establishing a centralized intake process that funnels requests into a single channel.
Improve the throughput of projects through the portfolio by incorporating the constraint of resource capacity to cap the amount of project approvals to that which is realistic.
Silence squeaky wheels and overbearing stakeholders by establishing a progressive approval and prioritization process that gives primacy to the highest value requests.
RE-DESIGN BUSINESS PROCESSES AND ENGAGE EMPLOYEES TO BEST UTILIZE ERP SOFTWAR...David McDonald
Change Solutions Group was engaged to work with company leadership, department managers, and employees, to streamline business practices and work processes and better utilize the new ERP software capabilities.
Choose the right software development methodology to boost efficiency and customer satisfaction. In this blog explore Lean development for optimized, quick product delivery.
How to create a strong team that is constantly trying to impriove processes and productivity.
Enables teams to determine how they would want to begin and maintain the journey.
An easy read plus descriptive materials to help teams setup strong improvement culture within the company and also within departments.
Agile software development development explainedServan Huegen
Explanation of different types of project approaches. From classic waterfall via Agile, Scrum, Kanban, LeSS, SAFe, Spotify Engineering Culture to Lean Startup and some eye opening tips and tricks.
1. Driving innovation 1
- Phil Thomson
CEO, Auror.
“The Build for Speed programme provided us with an
outsider’s perspective on our development processes
and has helped improve the way we work. We are
now more efficient and effective thanks to BFS.”
Build for Speed
Accelerating software development
2. Build For Speed 2
Build for Speed is a Callaghan
Innovation programme designed
to accelerate software development
and speed up project delivery.
3. Build For Speed 3
Speed: Reduce time to market for new products.
Software Development: Improve software development processes and architecture.
ROI: Realise business value and ROI sooner.
Cost-Effective: Reduce overheads by using test driven design.
Efficiency: Improve efficiency with automated testing tools and techniques.
Long Term: Improve long term effectiveness using continuous delivery principles.
What is
Build For Speed?
The intention of the programme is to increase throughput of software teams enabling them to keep up with the changing needs of the
business. The programme focuses on improving software architecture, managing technical debt and accelerating software development
through the application of continuous delivery principles. Build for Speed is split into two phases; Discovery and Deep Dive.
The Discovery process delivers up to 25 hours of provider support over 90 days, for a total cost of $5,000 plus GST.
Callaghan Innovation will co-fund 100% of this cost.
The Deep Dive process delivers up to 50 hours of provider support over 120 days, for a total cost of $10,000 plus GST.
Callaghan Innovation will co-fund 50% of this cost.
The majority of the two phases of the programme are delivered in the first 30 days. The remaining time is for follow up reviews.
Key Deliverables:
Build for Speed will deliver the following outcomes:
4. Build For Speed 4
Who should do
Build For Speed?
Businesses who are experiencing or are
expecting technical and capacity challenges
with scaling their business.
The process is suitable for both small and large organisations. The framework is flexible and can be adapted to match
the requirements of a specific organisation.
Understand what works well and where improvements can be made.
Embed new practices and skills in the organisation to create long term change.
Speed up software development and product delivery.
Improve their cost efficiency and realise a greater ROI– in a shorter timeframe.
Improve the scalability of their architecture and supporting technical practices.
5. Build For Speed 5
Outcomes
Common Issues Build for Speed
Difficulty scaling services to meet growing demand. Scalable
Architecture
Incremental improvements to fundamental architecture.
Older technology stack slowing down delivery.
Slowdowns due to organic product growth required to find early market focus.
FasterSoftware
Product
Evolution
Improvements to fundamental development processes and reduction in
technical debt.
Increasingly expensive to test new market ideas.
Trouble meeting timelines and unpredictable delivery.
Fewer Delays
and Less
Waste
Identify technical practices to improve throughput.
Multiple versions of software across client base leading to unsustainable
development and delivery.
Improved code management processes.
Problems in production. More than 5% of developer time spent fixing bugs. Long
test cycles.
Test driven design and the use of automation tools. Better system
monitoring.
Codebase that is difficult to maintain and change.
Identify code smells and learn how to refactor legacy code to make it
easier to change.
Over-reliance on a few individuals leading to higher risk. Difficulty retaining and/
or hiring good people. Continuous
Learning and
Development
Modernise software delivery practices to attract and retain the best
people and share knowledge and skills.
Need help identifying and implementing high value improvements.
Build an improvement backlog and introduce sustainable continuous
improvement practices. Regularly prioritise and implement high value
improvements. Review progress.
Difficulties while deploying changes to production. Complicated manual error
prone build/deploy/release process impacting quality and timing of deliverables.
Continuous
Delivery
Automate infrastructure, deployment and testing with Continuous
Delivery principles and DevOps culture.
Bottlenecks and blockers in development process, with work being ineffective. More Speed Smaller batch size for faster flow of value to customers.
6. Build For Speed 6
Process Overview
Engagement Phase
Discovery Process Phase Deep
Dive Phase
Pre-
Engagement
Assessment
Engagement
Plan
Review
Optional Stage II
Complete checklist of
pre-engagement.
Identify areas needing
improvement.
Create a technical
improvements backlog
and report.
Rank on time frames.
Agree metrics.
Select item(s) to be
addressed over 30/90
days.
Evaluate outcomes after
3 month;s and report to
Callaghan Innovation
on qualitative and
quantitative measures of
improvements.
The programme provides in-
house, hands on help, for the
company to address specific
items from the Discovery
Phase.
Discuss Statement of Works Agreement Service provider
Callaghan Innovation and the
business meet to discuss the
value in undertaking the Driving
Innovation process.
Provider to supply a Statement of
Works to the client business. The
client business is to agree and sign
before co-funding agreement can
be approved and signed.
Once agreement has been
reached to proceed a co-funding
Agreement is signed by Callaghan
Innovation and the client business.
Once the Agreement is in place the
appointed Service Provider works
with the Company to engage with
the appropriate staff and thought
leaders within the Company.
1 2 3 4
7. Build For Speed 7
Approach Outcomes Outputs
Time Frame, Cost and
Engagement Resources
1
Pre-
Engagement
Service Provider creates a checklist of
information for the business to provide,
including:
• Code samples.
• Internal assessments.
• Bug rates.
• Causal analysis.
• Documentation.
Provides insights into the business’
current state.
Samples of current activity
for discussion during the
assessment phase.
1 week. Development manager.
1 day of client time. Software developers.
Included in the total $5,000 cost
of the Discovery phase of the
programme.
100% co-funded by Callaghan
Innovation.
2
Assessment
Service provider will conduct a series of
interviews to assess current practices and
outcomes with a “stop-start-continue”
emphasis:
• Technical processes that should continue.
• Log of opportunities for improvement.
• Report on insights.
• Product vision, business and innovation
strategy.
• Work pipeline and team structure.
• Architectural overview.
• System design.
• Build process, branching strategy.
• Code review.
• Quality practices.
• Product development requirements.
• Project management.
Businesses get an understanding
of the level of their skills and
capabilities and areas of focus to
improve throughput.
Create a report of
the opportunities for
improvement and against
each a recommended action
to resolve.
2 weeks. Executive team members
who feed work inputs
to the software delivery
team.
Recognition across the business
that the factors affecting
throughput efficiency are from
across the organisation.
15-30 hours of client time.
Up to 20 hours of provider time.
Head of software delivery
and members of the
software team.
Included in the total $5,000 cost
of the Discovery phase of the
programme.
Programme Details
Discovery Process
8. Build For Speed 8
Approach Outcomes Outputs
Time Frame, Cost and
Engagement Resources
3
Engagement
Plan
Identify key opportunities for improvement. Recognition across the business
of how and which decisions affect
performance of the software
delivery team.
Deliver an action plan to
address the “key focus
opportunity” during the
programme.
1 week. Company Sponsor
and Head of Software
Delivery.
Jointly rank and prioritise for maximum
benefit.
The “key focus opportunity” is
addressed during the programme.
An action plan and time-
line to address all the areas
needing improvement as
agreed with the client.
1 hour of client time.
1 hour of provider time.
Callaghan Business
Innovation Advisor.
Create Action Plan covering specific steps
to be taken, outcomes expected, measures
of success, responsibilities and timeframes.
Organisations begin to work
collaboratively in delivering
increases in output.
Included in the total $5,000
cost of the Discovery phase of
the programme.
Customer Manager.
Identify “key focus opportunity.” Businesses are aware of their level
of technical debt.
4
Review
Company and Service Provider to jointly
review the process and the outcomes.
There is an increase in the quality
and delivery cadence of the
software teams.
3 month check in on
the business of progress
against the action plan and
identify any further remedial
assistance required.
1 week. Company Sponsor
and Head of Software
Delivery.
Meet with Callaghan Innovation to report,
evaluate and discuss outcomes.
Increased use of tools i.e.
automated testing, test driven
design.
Up to 2 hours of client time.
Up to 2 hours of provider time.
Discuss and agree next steps. Technical changes underway to
enable business demands for the
ability to scale to be met.
Included in the total $5,000
cost of the Discovery phase of
the programme.
Optional
Stage II
Select one or more of the action items
identified during the discovery phase.
Building in house capability through
transfer of expertise from service
provider
One or several of the action
items is addressed.
6 weeks ( 30 days). Key members of the
technical team.
The service provider will work
collaboratively with the team to help them
address the item selected.
Increase in delivery cadence
of the software team.
Over 40 hours of client time.
Up to 40 hours of provider time.
The 2 & 6 month check
in will be done with
the Callaghan Business
Innovation Advisor and/or
Customer Manager.
$10,000 (50% co-funded by
Callaghan Innovation).
Programme Details
Discovery Process (continued)
Deep Dive Process
9. Build For Speed 9
Content Coach
Workshops to explore and identify opportunities for improvement.
Focused coaching to provide advice and training.
Delivery Coach
Working directly in the business with your team.
Teaching and embedding new practices.
Identifying best practice champions.
On-the-job coaching and support to maximise outcomes.
Support
A Business Innovation Advisor ensures delivery quality is maintained and
delivery milestones are met.
The Business Innovation Advisor connects your business to the Callaghan
Innovation ecosystem.
Support Team
A Callaghan Innovation approved service provider will engage directly with your business. Two coaches will be appointed – for
Content and Delivery coaching respectively. Each programme engagement will be tailored to suit your business and will focus on
addressing areas needing improvement and building and maintaining areas of strength.
10. Build For Speed 10
Testimonials
“The Build for Speed programme provided expertise and guidance on the technical
practices we should focus on to improve the quality of our product. Involvement in this
programme gave the team a huge boost and we saw the benefits immediately. The real
gain though, is in the best practice measures that are now embedded in our business.”
Jill Tattersall
CEO,
Kiwa Digital
“The BFS programme helped us nail down areas
for improvement in terms of software development
process. The team was excellent at making rational
suggestions appropriate to us as to which of the
myriad of available tools in the market to use. In our
case the benefits are being realised slowly, but surely.
Now we are confident that our end goal in terms of
development process is sound.”
Bill Sim,
Engineering Manager,
Vigil Monitoring Ltd.
“The Build for Speed
programme was great at
connecting us with people
that could support the
organisational changes we
wanted. It really helped us
kick start the move to an
agile culture.”
Graeme Stretch,
COO,
Healthlink