Intro SWE Chapter 5 (B) Part Three
1. Visualize the Workflow
Kanban Method - Core practices of Kanban
2. Limit Work in Progress (WIP)
Kanban Method - Core practices of Kanban
3. Manage Flow
Kanban Method - Core practices of Kanban
4.Make Process Policies Explicit
Kanban Method - Core practices of Kanban
5. Implement feedback loops
Kanban Method - Core practices of Kanban
6. Improve Collaboratively (Using Models & the Scientific Method)
Kanban Method - Core practices of Kanban
Open-Source Software Development
Open-source software development is the process of developing open-source software. The software is developed and
distributed along with its source code, thus making it publicly accessible. Now, as it is available with the distributed license,
it permits the other programmers to use, modify and share the open-source software. During the open-source software
development, the programmer can add or fix a part of the software in order to make the software work properly.
Similarities between Open source & Agile methodology
small releases
informal,written communication using internet tools
customer avalibility
continuous integration
shared vision
Differences between Open source & Agile methodology
agile:
smaller teams
communication in Synchronous
small scale projects
Open Source:
Larger Teams
communication often Asynchronous
Large Scale Projects
DevOps definition
DevOps is a practice that allows a single team to manage the entire
application development life cycle: development, testing, deployment, and monitoring.
DevOps - Core elements
✓ Cultural: open mindedness and integration of information with mutual trust among all stake holder groups, including the
users.
✓ Automation: implementing and using high level of tools and automation, especially for CI/CD and testing.
✓ Lean: much like Kanban, minimize the WIP and applying lean principles to improve efficiency and speed across all aspects
of the product life cycle.
✓ Measurement: monitoring the overall system with key metrics for development, test, delivery, support, quality, user opinion,
value, etc.
✓ Sharing: free flow of information and knowledge along with sharing of responsibilities across all groups of development,
delivery, and operations.
Advantage(Pros) of Agile Method:
✓ Frequent Delivery
✓ Face-to-Face Communication with clients.
✓ Efficient design and fulfils the business requirement.
✓ Anytime changes are acceptable.
✓ Fast results and usable systems
✓ Low cost and low complexity
Disadvantages(Cons) of Agile Model:
Not scalable
Heavy reliance on teamwork
Reliance on frequent access to customer
Cultural clash
Disadvantages(Cons) of Agile Model with detail:
Not scalable:
Agile processes have been used by relatively small teams. Many projects are too big or too critical to be developed with Agile
methods.
o Heavy reliance on teamwork:
Not all people are able to work well in teams. Often, one bad member can destroy the cohesiveness of the entire team.
o Reliance on frequent access to customer:
Agile methods need frequent feedback from the customer. Not all customers are willing or able to provide this level of
cooperation and feedback. Without customer feedback, Agile methods are not able to validate requirements or adapt to change.
o Cultural clash:
Many XP practices clash with accepted software engineering wisdom, or with common management techniques. Performance
evaluations, for example, are harder to perform in XP because the work is done in pairs, and the code is owned by the whole
team.