The document discusses software maintenance and the agile approach. It defines software maintenance and the types of maintenance including corrective, adaptive, perfective, and preventative. It then contrasts the traditional and agile approaches to maintenance. The agile approach focuses on small iterative projects, prioritizing bugs based on customer input, automating testing and releases, and emphasizing practices like continuous integration, refactoring, and retrospectives to improve the process. Key challenges of maintenance discussed include ensuring team stability, transition planning, and dealing with fluctuating workloads.
What is Agile Project Management? | Agile Project Management | Invensis Learn...Invensis Learning
( *** PRINCE2 Agile Certification Training: https://bit.ly/2KIz6Oh *** )
( *** AgilePM Certification Training: https://bit.ly/2V3QhMf *** )
This presentation on What is Agile Project Management? explains the need for blending Agile concepts with control and governance of Project Management, also explains how it can be done.
Areas Covered:
1. Need for Agile Project Management
2. Understanding Principles of Agile & Project Management
3. What is Agile Project Management?
4. Difference Between Agile & Waterfall
5. Challenges if Agile Project Management
6. Understanding Agile Frameworks
7. Agile Project Management Career Paths
#AgileProjectManagement #InvensisLearning
Subscribe to our channel: https://bit.ly/3dmqNQS
Click here to check upcoming webinars on Agile Project Manager: https://goo.gl/M9v8oP
About Invensis Learning:
Invensis Learning is a pioneer in providing globally-recognized certification training courses for individuals and enterprises worldwide. We have trained and certified 15,000+ professionals from 50+ courses through multiple training delivery modes.
Invensis Learning provides live online certification training on Agile Project Management, there are two career paths one can opt for.
1. AgilePM certification by APMG: https://bit.ly/2V3QhMf
2. PRINCE2 Agile certification by AXELOS: https://bit.ly/2KIz6Oh
Upon enrolment, you will get lifetime access to a Learning Management System which will contain all class resources like recordings and Ppts, along with access to Agile Project Management webinars.
BECOME A CERTIFIED AGILE PROJECT MANAGER!
For more information please visit our website: https://www.invensislearning.com
Follow Us on:
Facebook: https://www.facebook.com/invensislearn/
LinkedIn: https://www.linkedin.com/company/inve...
Twitter: https://twitter.com/invensiselearn/
Deploying Hoshin Kanri as a Competitive WeaponGrant Crow
This presentation evaluates the Hoshin Kanri concept, what it is, how it works, what can go wrong and how to make Hoshin really work.
Slide 3: Most people familiar with Hoshin Kanri will know that it translates from Japanese into a "Vision Compass". More importantly, Hoshin is gaining traction due to its recognition of the need to link direction (strategy formulation) with management (implementation).
Slide 4: A key feature of Hoshin Kanri is the concept of Breakthrough Objectives. The concept encourages aggressive objectives together with a structured method for cascading these and breaking them down into manageable pieces.
Slides 5 and 6 address common responses from executives one might encounter when trying to introduce Hoshin Kanri together with the symptoms suggesting that Hoshin Planning is required. The symptoms listed will strike a chord with many readers and represent the product of poor strategy execution.
Slide 8 identifies some of the many leading organizations using Hoshin as their strategy execution methodology. The majority of organizations that we at i-nexus are talking to (particularly in the USA) are either considering implementing Hoshin Kanri or have already made a start.
Slide 9 identifies the value of having a strong strategy execution system by tracking share price performance.
Slides 11 and 12 introduce the link between Hoshin Kanri, and in particular the X matrix concept, and Balanced Scorecards. The traditional Balanced Scorecard clearly introduced value by looking at business metrics from more than purely a financial perspective. In contrast however, the X matrix is a far more robust tool for supporting strategy implementation. The various faces of the X matrix (South, West, North and East) detail the WHAT, HOW FAR, HOW and HOW MUCH of the strategy. Having said that, the X matrix is by no means universally popular as a Hoshin tool and is regarded by some CEO's as too complex. It is clearly a tool more likely to provide value in organizations that are more mature in their strategy execution journey.
Slide 13 shows an example of how the i-nexus software supports both the Hoshin X matrix and Scorecards.
Slide 15 identifies the critical role of the bowling chart in linking between the X matrix and action plans and its use a key management tool to track achievement and lack thereof against goals.
Slide 17 identifies "culture change" as a key barrier to effective Hoshin. Many of our customers do find that the greater transparency achieved with i-nexus can be seen as a threat. This needs to be managed carefully with problems (red traffic lights) seen as discussion points rather than failure.
Slide 22 provides an example of an A3 report. Many i-nexus customers find visual management of progress to be key to obtaining commitment to Hoshin.
Finally slide 24 looks at the value of Hoshin countermeasures in enabling early identification and resolution of barriers to progress.
What is Agile Project Management? | Agile Project Management | Invensis Learn...Invensis Learning
( *** PRINCE2 Agile Certification Training: https://bit.ly/2KIz6Oh *** )
( *** AgilePM Certification Training: https://bit.ly/2V3QhMf *** )
This presentation on What is Agile Project Management? explains the need for blending Agile concepts with control and governance of Project Management, also explains how it can be done.
Areas Covered:
1. Need for Agile Project Management
2. Understanding Principles of Agile & Project Management
3. What is Agile Project Management?
4. Difference Between Agile & Waterfall
5. Challenges if Agile Project Management
6. Understanding Agile Frameworks
7. Agile Project Management Career Paths
#AgileProjectManagement #InvensisLearning
Subscribe to our channel: https://bit.ly/3dmqNQS
Click here to check upcoming webinars on Agile Project Manager: https://goo.gl/M9v8oP
About Invensis Learning:
Invensis Learning is a pioneer in providing globally-recognized certification training courses for individuals and enterprises worldwide. We have trained and certified 15,000+ professionals from 50+ courses through multiple training delivery modes.
Invensis Learning provides live online certification training on Agile Project Management, there are two career paths one can opt for.
1. AgilePM certification by APMG: https://bit.ly/2V3QhMf
2. PRINCE2 Agile certification by AXELOS: https://bit.ly/2KIz6Oh
Upon enrolment, you will get lifetime access to a Learning Management System which will contain all class resources like recordings and Ppts, along with access to Agile Project Management webinars.
BECOME A CERTIFIED AGILE PROJECT MANAGER!
For more information please visit our website: https://www.invensislearning.com
Follow Us on:
Facebook: https://www.facebook.com/invensislearn/
LinkedIn: https://www.linkedin.com/company/inve...
Twitter: https://twitter.com/invensiselearn/
Deploying Hoshin Kanri as a Competitive WeaponGrant Crow
This presentation evaluates the Hoshin Kanri concept, what it is, how it works, what can go wrong and how to make Hoshin really work.
Slide 3: Most people familiar with Hoshin Kanri will know that it translates from Japanese into a "Vision Compass". More importantly, Hoshin is gaining traction due to its recognition of the need to link direction (strategy formulation) with management (implementation).
Slide 4: A key feature of Hoshin Kanri is the concept of Breakthrough Objectives. The concept encourages aggressive objectives together with a structured method for cascading these and breaking them down into manageable pieces.
Slides 5 and 6 address common responses from executives one might encounter when trying to introduce Hoshin Kanri together with the symptoms suggesting that Hoshin Planning is required. The symptoms listed will strike a chord with many readers and represent the product of poor strategy execution.
Slide 8 identifies some of the many leading organizations using Hoshin as their strategy execution methodology. The majority of organizations that we at i-nexus are talking to (particularly in the USA) are either considering implementing Hoshin Kanri or have already made a start.
Slide 9 identifies the value of having a strong strategy execution system by tracking share price performance.
Slides 11 and 12 introduce the link between Hoshin Kanri, and in particular the X matrix concept, and Balanced Scorecards. The traditional Balanced Scorecard clearly introduced value by looking at business metrics from more than purely a financial perspective. In contrast however, the X matrix is a far more robust tool for supporting strategy implementation. The various faces of the X matrix (South, West, North and East) detail the WHAT, HOW FAR, HOW and HOW MUCH of the strategy. Having said that, the X matrix is by no means universally popular as a Hoshin tool and is regarded by some CEO's as too complex. It is clearly a tool more likely to provide value in organizations that are more mature in their strategy execution journey.
Slide 13 shows an example of how the i-nexus software supports both the Hoshin X matrix and Scorecards.
Slide 15 identifies the critical role of the bowling chart in linking between the X matrix and action plans and its use a key management tool to track achievement and lack thereof against goals.
Slide 17 identifies "culture change" as a key barrier to effective Hoshin. Many of our customers do find that the greater transparency achieved with i-nexus can be seen as a threat. This needs to be managed carefully with problems (red traffic lights) seen as discussion points rather than failure.
Slide 22 provides an example of an A3 report. Many i-nexus customers find visual management of progress to be key to obtaining commitment to Hoshin.
Finally slide 24 looks at the value of Hoshin countermeasures in enabling early identification and resolution of barriers to progress.
Agile management, or agile process management, or simply agile refers to an iterative, incremental method of managing the design and build activities of engineering, information technology and other business areas that aim to provide new product or service development in a highly flexible and interactive manner; an example is its application in Scrum, an original form of agile software development.
Managing Requirements in Agile Development - Best Practices for Tool-Based Re...pd7.group
Agile software development leverages requirements management (RM) and offers many improvement opportunities for established RM practices. At the same time, agile RM must often be adopted to its specific application contexts and be combined with established RM. This is especially true for more complex areas like continuous product development and integrated hardware/software systems.
This presentation provides a brief overview of requirements management in the agile development lifecycle using methods like Scrum, XP, and Kanban. It introduces agile RM practices such as user stories and the Scaled Agile Framework (SAFeTM). Using examples from requirements tool Jama, the presentation illustrates how tool infrastructure can effectively support agile requirements management.
Contents of the presentation are:
- What is agile development? What is agile requirements management?
- Definition and agreement on agile user stories
- Requirements reviews & collaboration
- The interaction of requirements and tests in agile development
- Transition to agile RM
Introduction to Enterprise Agile FrameworksMehul Kapadia
* Need for Enterprise Agility
Agile practices have been adopted by organizations of all sizes.
For medium to large enterprises, team level agile practices have been stretched with custom fit processes and practices as needed to fulfill the gaps in end to end delivery life cycle.
* Agile@Scale
Enterprise Agile Frameworks have emerged to address the challenge of replicating agile success at organization level.
We will review following frameworks:
• SAFe – Scaled Agile Framework
• DAD – Disciplined Agile Delivery
• LeSS – Large Scale Scrum
* Attendees will leave this presentation with a clear understanding of current trends in organizational agility and will be able to take back the lessons learnt from speaker’s experience of SAFe implementation.
Agile/Scrum best Practices to improve quality.If some testing finds some defects, lot of testing would find lot of defects and improve quality. This presentation talks about few testing best practices that an agile team should follow for quality PI.
Kanban 101 workshop by John Goodsen and Michael Sahota.
This covers everything you will need to know to play Russell Healy's Kanban Game: visualizing the work, metrics, and creating explicit policies.
Slides are available on request. Please email me.
Learn about the DMAIC method that is used in Six Sigma. This Overview will walk you through Define, Measure, Analyze, Improve and Control in under 5 minutes. Learn more about the DMAIC method and other six sigma techniques on Lean Strategies International LLC's website: www.leanstrategiesinternational.com
Le DMAIC est une méthode de conduite de projet d’amélioration par percée des processus. Apparue il y a environ une trentaine d’années et aujourd’hui en plein essor dans les entreprises, elle permet d’obtenir des résultats spectaculaires. Quels sont ses secrets ?
Sommaire :
• Les fondamentaux du Lean et du 6 Sigma, l’association de ces 2 approches
• Les phases du DMAIC, leurs petits secrets…
• Des stats, mais pas trop !
• Pourquoi ça marche
• Comment réussir son projet DMAIC
Retrouvez le replay de cette web-conférence sur notre chaîne Youtube : http://buff.ly/2kWIQWD
Contains a quick review of the Scrum process, talks about the dangers of trying to map PMBOK to Scrum, and then tries to talk about the concepts behind managing an Agile project using Scrum.
Naresh and Shyam's experience report how teams and their interactions evolved at various large enterprise thru their agile transition in the last 5-6 years.
Agile management, or agile process management, or simply agile refers to an iterative, incremental method of managing the design and build activities of engineering, information technology and other business areas that aim to provide new product or service development in a highly flexible and interactive manner; an example is its application in Scrum, an original form of agile software development.
Managing Requirements in Agile Development - Best Practices for Tool-Based Re...pd7.group
Agile software development leverages requirements management (RM) and offers many improvement opportunities for established RM practices. At the same time, agile RM must often be adopted to its specific application contexts and be combined with established RM. This is especially true for more complex areas like continuous product development and integrated hardware/software systems.
This presentation provides a brief overview of requirements management in the agile development lifecycle using methods like Scrum, XP, and Kanban. It introduces agile RM practices such as user stories and the Scaled Agile Framework (SAFeTM). Using examples from requirements tool Jama, the presentation illustrates how tool infrastructure can effectively support agile requirements management.
Contents of the presentation are:
- What is agile development? What is agile requirements management?
- Definition and agreement on agile user stories
- Requirements reviews & collaboration
- The interaction of requirements and tests in agile development
- Transition to agile RM
Introduction to Enterprise Agile FrameworksMehul Kapadia
* Need for Enterprise Agility
Agile practices have been adopted by organizations of all sizes.
For medium to large enterprises, team level agile practices have been stretched with custom fit processes and practices as needed to fulfill the gaps in end to end delivery life cycle.
* Agile@Scale
Enterprise Agile Frameworks have emerged to address the challenge of replicating agile success at organization level.
We will review following frameworks:
• SAFe – Scaled Agile Framework
• DAD – Disciplined Agile Delivery
• LeSS – Large Scale Scrum
* Attendees will leave this presentation with a clear understanding of current trends in organizational agility and will be able to take back the lessons learnt from speaker’s experience of SAFe implementation.
Agile/Scrum best Practices to improve quality.If some testing finds some defects, lot of testing would find lot of defects and improve quality. This presentation talks about few testing best practices that an agile team should follow for quality PI.
Kanban 101 workshop by John Goodsen and Michael Sahota.
This covers everything you will need to know to play Russell Healy's Kanban Game: visualizing the work, metrics, and creating explicit policies.
Slides are available on request. Please email me.
Learn about the DMAIC method that is used in Six Sigma. This Overview will walk you through Define, Measure, Analyze, Improve and Control in under 5 minutes. Learn more about the DMAIC method and other six sigma techniques on Lean Strategies International LLC's website: www.leanstrategiesinternational.com
Le DMAIC est une méthode de conduite de projet d’amélioration par percée des processus. Apparue il y a environ une trentaine d’années et aujourd’hui en plein essor dans les entreprises, elle permet d’obtenir des résultats spectaculaires. Quels sont ses secrets ?
Sommaire :
• Les fondamentaux du Lean et du 6 Sigma, l’association de ces 2 approches
• Les phases du DMAIC, leurs petits secrets…
• Des stats, mais pas trop !
• Pourquoi ça marche
• Comment réussir son projet DMAIC
Retrouvez le replay de cette web-conférence sur notre chaîne Youtube : http://buff.ly/2kWIQWD
Contains a quick review of the Scrum process, talks about the dangers of trying to map PMBOK to Scrum, and then tries to talk about the concepts behind managing an Agile project using Scrum.
Naresh and Shyam's experience report how teams and their interactions evolved at various large enterprise thru their agile transition in the last 5-6 years.
"Release Early, Release Often" is a proven mantra, but what happens when you push this practice to it's limits? .i.e. deploying latest code changes to the production servers every time a developer checks-in code.
At Industrial Logic, developers are deploying code dozens of times a day, rapidly responding to their customers and reducing their "code inventory".
In this talk I explained the approach, deployment architecture, tools and culture needed for CD and how at Industrial Logic, we have gradually got there.
You can walk away with some good ideas of how your company can practice CD too.
You've heard about limiting WIP (Work-In-Progress) but how good are you at limiting red time? Red time is when you have compilation errors and/or failing tests. A growing group of practitioners have learned how to effectively reduce red time while test-driving and refactoring code. To understand how to limit red time, it helps to visualize it.
In this talk, Naresh Jain demonstrates various strategies to limit your time in Red. He analyzes live programming sessions using graphs that clearly visualize red time. You'll learn what programming processes help or hurt our ability to limit red time and you'll gain an appreciation for the visual cues that can help make you a better programmer and fellow member of the Limited Red Society.
Intent of this tutorial is to provide the participants with a hands-on-experience of real world refactoring by taking an open source project and refactoring it.
Benefits
After attending this session, the participants should be able to:
Build a common vocabulary in the refactoring space
Identify code smells
Eliminate code smells by applying the simple refactoring techniques explained in Martin Fowler‘s “Refactoring”
Write better unit/functional tests for legacy code
Understand some of the techniques and pitfalls in refactoring legacy code in the absence of unit and functional tests [”Working effectively with legacy code “]
Take existing code and refactor it to standard design patterns [Refactoring to patterns]
Learn about the internals of the open source project chosen to refactor
Know where to look to continue learning the techniques of refactoring
The objectives of this workshop are the following:
Use two 45 min activities to simulate the software development cycle. One will make use of a Waterfall approach, while the other will make use of an Agile approach to help participants experience the different outcomes of each methodology.
Introduce Agile as an adaptive, intuitive learning experience while cautioning participants that it is not a silver bullet. (People OVER Process.)
Demonstrate and emphasize the importance of communication and feedback on software projects. (Collaboration OVER Throw-It-Over-The-Wall.)
Assign participants to different roles that exist within a development team to help them look at software development from different perspectives and gain better understanding of and respect for team work.
"Before you write any code, make sure you have a failing test." This was a revolutionary idea, when it was first pitched in the late 90’s. Many successful entrepreneurs have been practicing a similar approach – "Before you build a product/service, make sure you have paying customers." In this talk, Naresh Jain shares his approach of finding effective MVPs to validate his Educational Product. Recently Naresh's article title "Sell before you build" was published by InfoQ http://www.infoq.com/articles/sell-before-you-build
ATDD - Acceptance Test Driven DevelopmentNaresh Jain
Acceptance test driven development tutorial. This tutorial explains how to take user stories and convert them into working software. Details about Acceptance Criteria and Acceptance tests using FitNesse and FitLibrary are described in this presentation. Also Patterns and Anti-Patterns associated with this are described in this presentation.
This is supposed to be an introductory presentation on Agile.
In this presentation I give some examples of heavy weight methods and their implications on your project. Then I give a quick overview of Agile methods, the rationale behind it, its origin, its values and principles. I move on to describe that what I see happening today in the industry is really waterfall in the name of Agile. I give some reasons why this is happening and then I give some pointers to move away from this flawed thinking.
Bottom line, Agile is not a Silver Bullet and don't fall pray to marketing gimmicks. Question dogmatic claims. Adapt Agile to your needs and take baby steps.
Value Driven Development by Dave Thomas Naresh Jain
Agile, OOP... are like good hygiene in the kitchen, it results in meals with consistent quality and predictable prep and service times. It doesn't result in great meals nor substantially impact the ROI! Lean Thinking clearly shows that the only way to make a significant impact is to improve the value chain by improving flow. If everyone is following best practices no one has competitive advantage. Major improvements in the value chain depend on continued disruptive innovations. Innovations leverage people and their ideas. We use case studies to illustrate the different business and technical innovations and their impact. We conclude with a discussion of how to build and leverage an innovation culture versus a sprint death march when dealing with high value time to market projects.
More details: https://confengine.com/agile-india-2017/proposal/3608/value-driven-development-maximum-impact-maximum-speed
What is DevOps?
Why DevOps?
How DevOps works?
DevOps impacts in testing.
Continuous Delivery.
Continuous Integration.
Continuous Testing and Automated Deployment.
These slides, covering the topics of Software Maintenance and Evolution, are introductory slides to the course LINGI2252 “Software Maintenance and Evolution”, given by Prof. Kim Mens at UCL, Belgium
Continuous Automation and its Impact on the CI_CD Pipeline.pdfkalichargn70th171
The CI/CD pipeline ensures software development teams reliably deliver code changes. CI is Continuous Integration, where developers merge code changes into a central repository, followed by automatic builds and tests. CD is either Continuous Delivery or Continuous Deployment, which are practices that automate the delivery of applications to selected infrastructure environments. Continuous Delivery automates the delivery process, while Continuous Deployment automates the production release.
John Fodeh - Adventures in Test Automation-Breaking the Boundaries of Regress...TEST Huddle
EuroSTAR Software Testing Conference 2012 presentation on Adventures in Test Automation-Breaking the Boundaries of Regression Testing by John Fodeh.
See more at: http://conference.eurostarsoftwaretesting.com/past-presentations/
ROLE OF iSAFE/iMobi IN SEAMLESS INTEGRATION OF THE DEVOPS ENVIRONMENTIndium Software
IP-led test automation framework supported by blueprint
for product development in Devops environment can
ensure automation in the true sense.
DevOps is fast becoming adopted as the environment for product
development. It facilitates closer integration of development and operations
teams, reducing the time needed to develop and deploy a product. However,
it is still in its early stages and the teams continue to work in silos due to the
different kinds of tools they need suited to their needs.
An IP-driven testing framework like iSAFE can be the bulwark on which the development, testing and operations teams can integrate more seamlessly,
as it provides one key feature needed when handling such a comprehensive
environment – traceability. The other advantages, of course, are reusability,
automated alerts and shorter testing periods, thus aiding in the quick time-to-market
needs of the organizations.
Live Webinar- Making Test Automation 10x Faster for Continuous Delivery- By R...RapidValue
A live webinar hosted by RapidValue Solutions on "Making Test Automation 10X Faster for Continuous Delivery".
Key takeaways:
1. Achieving test automation in a DevOps world
2. Building a business-tailored test automation framework
3. Overcoming limitations of open source tools
4. Case study: Creating 2000+ test cases in less than a month for a product development firm
5. Demo: Zero-code test automation for non-testers using AccuRate ( test automation suite by RapidValue)
Problem Solving Techniques For Evolutionary DesignNaresh Jain
In this workshop, Naresh Jain explains what are the core techniques one should master to effectively practice evolutionary design while solving real-world problems. To summarize:
1. Eliminate Noise - Distill down the crux of the problem
2. Divide and Conquer to prioritize and focus on the most important part
3. Add constraints to future simplify the problem
4. Come up with a simple design to incrementally build your solution
5. Refactor: Pause, look for a much simpler alternative
6. Be ready to throw away your solution & start again
Agile India 2019 Conference Welcome NoteNaresh Jain
We are super excited to announce the 15th edition of Agile India 2019, Asia's Largest and Premier International conference on Leading Edge Software Development Methods. Agile India is hosted by Agile Alliance and organized by Agile Software Community of India, a non-profit registered society founded in 2004 with a vision to evangelize new, better ways of building products & services that delight the users.
Over the last 15 years, we've organized 57 conferences across 13 cities in India. We've hosted 1,000+ speakers from 38 countries, who have delivered 1,200+ sessions to 10,000+ attendees. We continue to be a non-profit, volunteer-run community conference.
Agenda
* Agile Coach Camp - March 17th
* Pre-Conference Workshops – March 18th
* Conference Days
** Agile Mindset Day - March 19th
** Business Agility Day - March 20th
** Design Innovation Day - March 21st
** Continuous Delivery and DevOps Day - March 22nd
* Post-Conference Workshops – March 23rd and 24th
More details: https://2019.agileindia.org
A resilient organizational can not only adapt and respond to incremental change but more importantly, can respond to sudden disruptions and also, be the source of disruption in order to prosper and flourish.
The traditional risk management approach focuses too much on defensive (stopping bad things happen) thinking versus a more progressive (making good things happen) thinking. Being defensive requires consistency across the organization and this is where methodologies like Plan-Do-Check-Act (PDCA) come in. However, PDCA approach does not bake in the required progressive thinking and flexibility required for a fast company organization which operates in a volatile environment.
Professor David Denyer of Cranfield University has recently published a very interesting research report on Organizational Resilience. He has identified the following four quadrants across to help us think about organizational resilience:
* preventative control (defensive consistency)
* mindful action (defensive flexibility)
* performance optimization (progressive consistency)
* adaptive innovation (progressive flexibility)
In this talk, I'll share my personal experience of using this thinking to help an organization to scale their product to Millions of users. I've dive deep into how we structured our organization for Structural Agility and how we set-up a very lightweight governance model using OKRs to drive the necessary flexible and progressive thinking.
More details: https://confengine.com/agile-india-2019/proposal/8216/organisational-resilience-design-your-organisation-to-flourish-not-merely-survive
Conference Link: https://2019.agileindia.org
Looking to move to Continuous Delivery? Worried about the quality of your the code? Helping your developers understand clean-code practices and getting the right testing strategy in place can take a while. What should you do to control the quality of the incoming code till then? This talk shares our experience of using PRRiskAdvisor to gradually educate and influence developers to write better code and also help the code reviewer to be more effective at their reviews.
Every time a developer raises a pull-request, PRRiskAdvisor analyzes the files that were changed and publishes a report on the pull request itself with the overall risk associated with this pull request and also risk associated with each file. It also runs static code analysis using SonarQube and publishes the configured violations as comments on the pull request. This way the reviewer just has to look at the pull request to get a decent idea of what it means to review this pull request. If there are too many violations, then PRRiskAdvisor can also automatically reject the pull request.
By doing this, we saw our developers starting paying more attention to clean code practices and hence the overall quality of the incoming code improved, while we worked on putting the right engineering practices and testing strategy in place.
More details: https://confengine.com/last-conference-canberra-2018/proposal/7294/improving-the-quality-of-incoming-code
Conference Link: https://2019.agileindia.org
Here is a quick summary of Agile India 2018 Conference, Asia's Largest and Premier Conference on Business Agility, Design Innovation, Digital Transformation, Continuous Delivery, DevOps, Agile, Scrum, eXtreme Programming, Lean, Kanban, Enterprise Agile, Lean Startup, Research, and Patterns. Get to meet pioneers and expert practitioners from around the world on Agile Mindset, Scaling Agility, Lean Product Discovery, Continuous Delivery and DevOps. 4 - 11 March 2018 at Taj West End, Bangalore. More details: https://2018.agileindia.org
We are very excited to announce the 14th edition of Agile India Conference (https://2018.agileindia.org/) with brand new themes and a fabulous lineup of speakers. Agile India is Asia's Largest & Premier International conference on Leading Edge Software Development Methods.
Meet:
* Alan Cooper - The Father of Visual Basic, Creator of Goal-directed Design methodology and inventor of the Persona concept
* Steve Denning - Author of several books on Management, Leadership, Innovation and Organizational Storytelling
* Linda Rising - Author of four books, most recently the Fearless Change
* Gregor Hohpe - Author of Enterprise Integration Patterns. Technical Director at Google Cloud Computing
* James Stewart - Co-founder of the Government Digital Service and x-Deputy CTO of the UK Government
* Bjarte Bogsnes - Author of Implementing Beyond Budgeting, Chairman of Beyond Budgeting Roundtable and Senior Advisor Performance Framework at Statoil
* Dr. Denis Bauer - Team Leader and Research Scientist in Cloud Computing in Transformational Bioinformatics at CSIRO
* Jeff Patton - Author of User Story Mapping and the person responsible for bringing user-centered design thinking to Agile world
* Peter Jacobs - Chief Information Officer and board member of ING Bank Netherlands
* Nils Kappeyne - VP & CIO for Integrated Gas & New Energies at Shell
* And 70 more thought leaders from 16 countries - https://2018.agileindia.org/speakers/
The program spreads across 8 days (March 4-11th 2018, Bengaluru) with two pre-conference plus two post-conference workshop days and four days of conferences in between:
* March 4-5th: Pre-Conference Workshops from our international experts
* March 6th: Business Agility Day - Hosted by Agile Alliance
* March 7th: Design Innovation Day - Hosted by Cooper
* March 8th: Digital Transformation Day
* March 9th: DevOps and Continuous Delivery Day - Hosted by Red Hat
* March 10-11th: Post-Conference Workshops from our international experts
Schedule
========
Check out conference schedule for the lineup of workshops and speakers. https://confengine.com/agile-india-2018/schedule
Tickets
=======
Conference registration is now open and Smart Price offers are going away soon. Register now for best deals!! https://confengine.com/agile-india-2018/register
Check out the exciting offers for bulk registrations - https://2018.agileindia.org/agile-india-2018-bulk-booking-offers/.
Sponsors
========
We thank Agile Alliance, Cooper, RedHat, Scrum.org, Shell, AddTeq/Atlassian, Scaled Agile, ICAgile and Scrum Alliance for sponsoring the conference. If your organization wants to support this non-profit, volunteer-run conference, please check out sponsorship options https://confengine.com/agile-india-2018/sponsor#guide
Agile India 2018 Conference is Asia's Largest and Premier Conference on Business Agility, Design Innovation, Digital Transformation, Continuous Delivery, DevOps, Agile, Scrum, eXtreme Programming, Lean, Kanban, Enterprise Agile, Lean Startup, Research, and Patterns. Get to meet pioneers and expert practitioners from around the world on Agile Mindset, Scaling Agility, Lean Product Discovery, Continuous Delivery and DevOps. 4 - 11 March 2018 at Taj West End, Bangalore. More details: https://2018.agileindia.org
Agile India 2018 Conference is Asia's Largest and Premier Conference on Business Agility, Design Innovation, Digital Transformation, Continuous Delivery, DevOps, Agile, Scrum, eXtreme Programming, Lean, Kanban, Enterprise Agile, Lean Startup, Research, and Patterns. Get to meet pioneers and expert practitioners from around the world on Agile Mindset, Scaling Agility, Lean Product Discovery, Continuous Delivery and DevOps. 4 - 11 March 2018 at Taj West End, Bangalore. More details: https://2018.agileindia.org
Pilgrim's Progress to the Promised Land by Robert VirdingNaresh Jain
When migrating to Elixir/OTP from other languages and systems a number of issues will always crop up. The trick is to make sure that these issues don't become problems. This talk will look at some of the more common ones and what to do about them to make sure they don't become problems.
More details: https://confengine.com/functional-conf-2017/proposal/5138/pilgrims-progress-to-the-promised-land
Conference: https://functionalconf.com
Concurrent languages are Functional by Francesco CesariniNaresh Jain
The functional paradigm has been influencing mainstream languages for decades, making developers more efficient whilst helping reduce software maintenance costs. As we are faced with a programming model that needs to scale on multi-core architectures, concurrency becomes critical. In these concurrency models, the functional programming paradigm will become even more evident. To quote Simon Peyton Jones, future concurrent languages will be functional; they might not be called functional, but the features will be.
Using his 20 years of programming and teaching Erlang/OTP, Francesco will walk through the functional programming features that make implementations of the actor model viable in the Erlang ecosystem. These are features we might take for granted or do not think about, but have laid the foundation of multi-core and distributed programming, influencing programming languages, old and new.
More details: https://confengine.com/functional-conf-2017/proposal/4774/concurrent-languages-are-functional
Erlang from behing the trenches by Francesco CesariniNaresh Jain
Erlang is a programming language designed for the Internet Age, although it pre-dates the Web. It is a language designed for multi-core computers, although it pre-dates them too. It is a “beacon language”, to quote Haskell guru Simon Peyton-Jones, in that it more clearly than any other language demonstrates the benefits of concurrency-oriented programming. In this talk, I will introduce Erlang from behind the trenches. By introducing the major language constructs, describe their benefits and discuss the problems Erlang is ideal to solve. I will be doing so from a personal prospective, with anecdotes from my time as an intern at the Ericsson computer science lab at a time when the language was being heavily influenced and later when working on the OTP R1 release.
More details: https://confengine.com/functional-conf-2017/proposal/4787/an-introduction-to-erlang-from-behind-the-trenches
Anatomy of an eCommerce Search Engine by Mayur DatarNaresh Jain
In this talk, the chief Data scientist of Flipkart will uncover the various challenges in running an e-commerce search platform like scale, recency, update rates, business shaping etc. He will also explain the overall system architecture of the search platform and get into the details of some of the sub-systems, including the query understanding and rewriting sub-system.
Setting up Continuous Delivery Culture for a Large Scale Mobile AppNaresh Jain
Hike is a mobile-first, messaging platform that is used by 100 million users to exchange 40 billion messages/month. Hike app is available on Android, iOS and Windows phone. On the back-end, we’ve 100+ macro-services in Java, Python, Ruby, Go and Elixir. While setting up a Continuous Delivery pipeline, we ran into a series of technical challenges. However it was more important to address the organisational/behavioural challenges to ensure a sustainable culture shift in the company.
In this talk, I cover how we went about:
* Setup a trunk-based development model
* Decentralised our build & test environments using Docker and Jenkins
* Segregated and containerised our macro-services
* Refactored the mobile apps to be more container friendly
* Setup a mobile device farm using STF
* Improved the quality of code-reviews using PRBuilder & PRRiskAdvisor
* Created different kinds of automated tests to align with our CI Pipeline and get rapid feedback
* Finally how we used C3 to visualise the health of our code-base
Towards FutureOps: Stable, Repeatable environments from Dev to ProdNaresh Jain
Modern human history is a story of humans inventing new tools to do more with less. "Doing more" has allowed most of us to no longer worry about producing our own food, collecting water, planning long journeys, etc. Instead, we’re able to specialize, buy what we need for less, and to some extent explore ourselves a lot more.
We're far from done, and of course humanity is far from perfect. In this talk, Mitchell Hashimoto discusses the role that automations and computers play in building a brighter future.
More details: https://confengine.com/agile-india-2017/proposal/3618/towards-futureops-stable-repeatable-environments-from-dev-to-prod
No Silver Bullets in Functional Programming by Brian McKennaNaresh Jain
We are constantly presented with trade-offs when writing software. What are the trade-offs when applying functional programming? What costs arise? When is it not worth doing? When should pragmatism kick in and when should we start using side-effects?
This talk will give you some tools to be able to answer the above questions for both functional programming and types. The tools have been refined over many professional years of both doing and not doing purely functional programming.
More details: https://confengine.com/functional-conf-2016/proposal/3137/no-silver-bullets-in-functional-programming
For over 35 years, functional programming has been a hot research topic. However in the last 5 years, driven by the need to build massively concurrent systems and to handle big-data, we have experienced a rapid adoption of functional programming concepts by diverse companies, ranging from tech start-ups to financial institutes.
These days, functional programming is at the heart of every, new generation programming technologies. Companies are employing functional programming to enable more effective, robust, and flexible software development. This has given birth to a very vibrant community of functional programmers, who are constantly exploring ways to bring functional programming concepts to the world of enterprise software development.
Functional Conf is designed to bring the growing community of functional programmers together under one roof. At Functional Conf:
participants can understand the fundamentals concepts behind functional programming,
they can learn how others are using functional programming to solve real world problems,
practitioners can meet peers and exchange their experience,
experts can share their expertise on practical usage and gotchas in functional programming concepts.
More details: http://functionalconf.com/ or https://confengine.com/functional-conf-2016
Agile India 2017 Conference is Asia's Largest and Premier Conference on Agile, Scrum, eXtreme Programming, Lean, Kanban, DevOps, Enterprise Agile, Lean Startup, Continuous Delivery, Research and Patterns. Get to meet pioneers and expert practitioners from around the world on Agile Mindset, Scaling Agility, Lean Product Discovery, Continuous Delivery and DevOps. 6 - 12 March 2017 at ITC Gardenia, Bangalore. More details: http://2017.agileindia.org
This talk will explain the secret of the success of the Eclipse Platform team. The Eclipse Way is an agile software development process that we started right at the beginning when we started to develop Eclipse back in 1999. It was and is used by the Eclipse Platform team and got continuously improved over time. During the session you will hear about all our practices, like milestones, early and iterative planning, continuous integration and the endgame. I will also reveal some of the history behind the Eclipse top-level project.
More details: https://confengine.com/eclipse-summit-2016/proposal/2386/the-eclipse-way
Unleashing the Power of Automated Refactoring with JDTNaresh Jain
Refactoring is a series of small steps, each of which changes the program’s internal structure without changing its external behaviour. Refactoring, as a tool, to automate behaviour-preserving transformations to source code are not only very popular in agile development environments, but have been widely established as a cornerstone of the daily software development process, regardless of the methodology being used. Most major development environments such as Eclipse offer a set of powerful refactoring to substantially increase development productivity.
In this live demo, I’ll show
* the real value of refactoring,
* how we practice it safely,
* when and why we refactor,
* the power of refactoring tools and
* when we avoid refactoring.
I’ll be using two real-world examples of refactoring and sharing what I’ve learned about this important practice of the last 15 years.
Getting2Alpha: Turbo-charge your product with Game Thinking by Amy Jo KimNaresh Jain
Do you want to harness the deeper power of games – the power to drive long-term engagement? Are you ready to look beyond the silver bullets & Skinner boxes – and learn to think like a game designer? In this talk, you’ll learn the foundations of Game Thinking - brought to life with front-line stories from eBay, Ultima Online, The Sims, Rock Band, Covet Fashion, Happify, Lumosity and Slack. You’ll come away with a smarter approach to innovative product design - and practical, actionable design tips you can use right away to turbo-charge your path towards product/market fit.
More details: https://confengine.com/agile-india-2016/proposal/1961/getting2alpha-turbo-charge-your-product-with-game-thinking
US Economic Outlook - Being Decided - M Capital Group August 2021.pdfpchutichetpong
The U.S. economy is continuing its impressive recovery from the COVID-19 pandemic and not slowing down despite re-occurring bumps. The U.S. savings rate reached its highest ever recorded level at 34% in April 2020 and Americans seem ready to spend. The sectors that had been hurt the most by the pandemic specifically reduced consumer spending, like retail, leisure, hospitality, and travel, are now experiencing massive growth in revenue and job openings.
Could this growth lead to a “Roaring Twenties”? As quickly as the U.S. economy contracted, experiencing a 9.1% drop in economic output relative to the business cycle in Q2 2020, the largest in recorded history, it has rebounded beyond expectations. This surprising growth seems to be fueled by the U.S. government’s aggressive fiscal and monetary policies, and an increase in consumer spending as mobility restrictions are lifted. Unemployment rates between June 2020 and June 2021 decreased by 5.2%, while the demand for labor is increasing, coupled with increasing wages to incentivize Americans to rejoin the labor force. Schools and businesses are expected to fully reopen soon. In parallel, vaccination rates across the country and the world continue to rise, with full vaccination rates of 50% and 14.8% respectively.
However, it is not completely smooth sailing from here. According to M Capital Group, the main risks that threaten the continued growth of the U.S. economy are inflation, unsettled trade relations, and another wave of Covid-19 mutations that could shut down the world again. Have we learned from the past year of COVID-19 and adapted our economy accordingly?
“In order for the U.S. economy to continue growing, whether there is another wave or not, the U.S. needs to focus on diversifying supply chains, supporting business investment, and maintaining consumer spending,” says Grace Feeley, a research analyst at M Capital Group.
While the economic indicators are positive, the risks are coming closer to manifesting and threatening such growth. The new variants spreading throughout the world, Delta, Lambda, and Gamma, are vaccine-resistant and muddy the predictions made about the economy and health of the country. These variants bring back the feeling of uncertainty that has wreaked havoc not only on the stock market but the mindset of people around the world. MCG provides unique insight on how to mitigate these risks to possibly ensure a bright economic future.
Turin Startup Ecosystem 2024 - Ricerca sulle Startup e il Sistema dell'Innov...Quotidiano Piemontese
Turin Startup Ecosystem 2024
Una ricerca de il Club degli Investitori, in collaborazione con ToTeM Torino Tech Map e con il supporto della ESCP Business School e di Growth Capital
how can I sell pi coins after successfully completing KYCDOT TECH
Pi coins is not launched yet in any exchange 💱 this means it's not swappable, the current pi displaying on coin market cap is the iou version of pi. And you can learn all about that on my previous post.
RIGHT NOW THE ONLY WAY you can sell pi coins is through verified pi merchants. A pi merchant is someone who buys pi coins and resell them to exchanges and crypto whales. Looking forward to hold massive quantities of pi coins before the mainnet launch.
This is because pi network is not doing any pre-sale or ico offerings, the only way to get my coins is from buying from miners. So a merchant facilitates the transactions between the miners and these exchanges holding pi.
I and my friends has sold more than 6000 pi coins successfully with this method. I will be happy to share the contact of my personal pi merchant. The one i trade with, if you have your own merchant you can trade with them. For those who are new.
Message: @Pi_vendor_247 on telegram.
I wouldn't advise you selling all percentage of the pi coins. Leave at least a before so its a win win during open mainnet. Have a nice day pioneers ♥️
#kyc #mainnet #picoins #pi #sellpi #piwallet
#pinetwork
The Evolution of Non-Banking Financial Companies (NBFCs) in India: Challenges...beulahfernandes8
Role in Financial System
NBFCs are critical in bridging the financial inclusion gap.
They provide specialized financial services that cater to segments often neglected by traditional banks.
Economic Impact
NBFCs contribute significantly to India's GDP.
They support sectors like micro, small, and medium enterprises (MSMEs), housing finance, and personal loans.
Even tho Pi network is not listed on any exchange yet.
Buying/Selling or investing in pi network coins is highly possible through the help of vendors. You can buy from vendors[ buy directly from the pi network miners and resell it]. I will leave the telegram contact of my personal vendor.
@Pi_vendor_247
Falcon stands out as a top-tier P2P Invoice Discounting platform in India, bridging esteemed blue-chip companies and eager investors. Our goal is to transform the investment landscape in India by establishing a comprehensive destination for borrowers and investors with diverse profiles and needs, all while minimizing risk. What sets Falcon apart is the elimination of intermediaries such as commercial banks and depository institutions, allowing investors to enjoy higher yields.
how can i use my minded pi coins I need some funds.DOT TECH
If you are interested in selling your pi coins, i have a verified pi merchant, who buys pi coins and resell them to exchanges looking forward to hold till mainnet launch.
Because the core team has announced that pi network will not be doing any pre-sale. The only way exchanges like huobi, bitmart and hotbit can get pi is by buying from miners.
Now a merchant stands in between these exchanges and the miners. As a link to make transactions smooth. Because right now in the enclosed mainnet you can't sell pi coins your self. You need the help of a merchant,
i will leave the telegram contact of my personal pi merchant below. 👇 I and my friends has traded more than 3000pi coins with him successfully.
@Pi_vendor_247
Exploring Abhay Bhutada’s Views After Poonawalla Fincorp’s Collaboration With...beulahfernandes8
The financial landscape in India has witnessed a significant development with the recent collaboration between Poonawalla Fincorp and IndusInd Bank.
The launch of the co-branded credit card, the IndusInd Bank Poonawalla Fincorp eLITE RuPay Platinum Credit Card, marks a major milestone for both entities.
This strategic move aims to redefine and elevate the banking experience for customers.
If you are looking for a pi coin investor. Then look no further because I have the right one he is a pi vendor (he buy and resell to whales in China). I met him on a crypto conference and ever since I and my friends have sold more than 10k pi coins to him And he bought all and still want more. I will drop his telegram handle below just send him a message.
@Pi_vendor_247
What price will pi network be listed on exchangesDOT TECH
The rate at which pi will be listed is practically unknown. But due to speculations surrounding it the predicted rate is tends to be from 30$ — 50$.
So if you are interested in selling your pi network coins at a high rate tho. Or you can't wait till the mainnet launch in 2026. You can easily trade your pi coins with a merchant.
A merchant is someone who buys pi coins from miners and resell them to Investors looking forward to hold massive quantities till mainnet launch.
I will leave the telegram contact of my personal pi vendor to trade with.
@Pi_vendor_247
The European Unemployment Puzzle: implications from population agingGRAPE
We study the link between the evolving age structure of the working population and unemployment. We build a large new Keynesian OLG model with a realistic age structure, labor market frictions, sticky prices, and aggregate shocks. Once calibrated to the European economy, we quantify the extent to which demographic changes over the last three decades have contributed to the decline of the unemployment rate. Our findings yield important implications for the future evolution of unemployment given the anticipated further aging of the working population in Europe. We also quantify the implications for optimal monetary policy: lowering inflation volatility becomes less costly in terms of GDP and unemployment volatility, which hints that optimal monetary policy may be more hawkish in an aging society. Finally, our results also propose a partial reversal of the European-US unemployment puzzle due to the fact that the share of young workers is expected to remain robust in the US.
3. Agenda of this discussion
Glossary
Why maintain software
Types of Software Maintenance
Traditional v/s Agile Maintenance Approach
Agile Testing
Agile Release Management
Why maintenance is so expensive (and can be destructive)
Agile Maintenance Best Practices
Conclusion
Q&A
3
4. Glossary
Software maintenance is defined as the process of modifying
a software system or component after delivery to correct
faults, improve performance or other attributes, or adapt to a
changed environment [IEEE 1990]
Iterative Agile Development
What’s the difference between Maintenance and Support?
ADD MAX VALUE TO THE CLIENT !
4
5. Why maintain software?
Stephen R Schach summarizes:
• Model of reality. As the reality changes, the software must adapt or die.
• Pressures from satisfied users, to extend the functionality of the
product.
• Software is much easier to change than hardware. As a result, changes
are made to the software whenever possible.
• Successful software survives well beyond the lifetime of the
environment for which it was written.
5
6. Types of Software Maintenance
• Corrective maintenance is maintenance performed to correct faults
in hardware or software [IEEE 1990]
• Adaptive maintenance is software maintenance performed to make
a computer program usable in a changed environment [IEEE 1990].
• Perfective maintenance is software maintenance performed to
improve the performance, maintainability, or other attributes of a
computer program. [IEEE 1990]
• Preventative maintenance is maintenance preformed for the
purpose of preventing problems before they occur [IEEE 1990]
6
7. The Frequency of Each Type of
Maintenance
Types of Maintenance
4%
17%
Corrective (fixing faults)
Perfective (new functionality)
Adaptive (environmental changes)
18% 61%
Other
7
8. Traditional v/s Agile Maintenance
Approach
Traditional approach Agile approach
1. Massive projects with waterfall model 1. Small projects with agile model
2. CR Form 2. Bug reports / story cards
3. Change control board [CCB]
4. CCB approves and prioritizes the bugs 3. Developers estimate
4. Customer prioritizes the bugs
5. Summary of the bugs handed over to 5. Common bug tracking database
the developers – loss of context
6. Developers jump to the code and fix it 6. QAs test and write functional
7. Update all the design documents acceptance tests
7. Developers write failing unit tests
8. Developers fix it and run unit &
functional tests
8. Regression testing 9. Regression testing
9. Patch release 10. New release
8
9. Quick Fix or Iterative Development
• Quick fix is often used in emergency, corrective maintenance.
Emergency maintenance is unscheduled corrective maintenance
performed to keep a system operational [IEEE 1998]. Also called
Code & Fix
• Iterative development process is based on the Evolutionary
development paradigm [Takang and Grubb 1996] or Extreme
Programming paradigm.
• Iterative enhancement involves a five-staged cycle:
Analysis (simulation)
User acceptance tests and Unit tests
Redesign and implementation
Regression tests
Release
9
10. Agile Maintenance Testing
• Acceptance Testing – xUnit, FIT, …
• Unit Tests – Black box functional unit tests
• Regression testing is selective retesting of a system or
component to verify that modifications have not caused
unintended effects and that the system or component still
complies with its specified requirements [IEEE 1990]
10
11. Agile Release Management
Software release management, also known as software
configuration management, is the management of activities
surrounding release of one or more versions of software to one
or more customers. Release management includes defining
acceptable quality levels for release, authority to authorize the
release, release procedures, and so on [IEEE 1990].
Best practices:
• Automated release creation and verification process
• Automated management of application specific configuration
• Simulation of target deployment environments and automated
testing
• Release creation from the QA environment
11
12. Maintenance Smells
• A lot of regression bugs
• Less than 50% of the time is dedicated to refactoring
• Developers not pairing 100%
• Test coverage not improving with time
• Lack of team outings
• People getting stuck on the project for more than a year
12
13. Why Maintenance Is So Expensive
(and Can Be Destructive)?
• Team stability
• Contractual responsibility
• Staff skills
• Transition plan for team members
• Program age and structure
• Stressful nature of work
• Fluctuation in the workload and resourcing problems
• Planning
13
14. Agile Maintenance Best Practices
• Automated regression testing
• Continuous integration
• Coding standard
• Developers can focus on maintainability -
Refactoring
• Pair programming
• Application logs
• Bug Tracking database – Knowledge repository
• Retrospectives
14
15. Agile Maintenance Best
• Practices…
QA – Developer pairing
• Debugging is parallelizable
• Involve your customer – Daily status, Project Wiki
in Customer environment, IM conversations, IPM,
• Constantly improve the test coverage
• Use some acceptance test framework
• QA smoke test on the developer machine for
immediate feedback
• Short releases
15
16. My 0.02
• Source code is the king
• Untrustworthy documentation
• The bug-tracking database stores knowledge
• Reproduction is essential to obtaining a
solution
16