Choosing The

Right Agile Prabhat Sinha Methodology Shani Memfy For Your Drupal Project Speakers

Prabhat Sinha Shani Memfy

He has been managing product and She’s been managing product and project project since 8 years. After work Prabhat deliveries since 1999. After work you can can be found jogging and socializing at find her on the court shooting hoops with local parks. a local Netball league.

Prabhat lives in the bustling city New Delhi Shani lives in a suburban city in Israel with with his wife and 2 kids. her husband and 4 children. Agenda

1. What is Agile 2. Agile Frameworks ● Scrum ● KANBAN ● Scrumban ● Extreme Programming ● Lean ● Feature Driven development 3. Comparison 4. CYNEFIN What is Agile?

Better ways of developing software is by doing it and helping others do it. Agile gives importance to:

● Individuals and interactions over processes and tools

● Working software over comprehensive documentation

● Customer collaboration over contract negotiation

● Responding to change over following a plan 12 Principles of Agile Manifesto

Our highest priority is Welcome changing requirements, Deliver working software frequently, 01 to satisfy the customer 02 even late in development. Agile 03 from a couple of weeks lo a couple through early and processes harness change for the of months, with a preference to the continuous delivery of customer’s competitive advantage. shorter timescale. valuable software.

04 Business people and 05 Build projects around motivated 06 Agile processes promote developers must work individuals. Give them the sustainable development. The together daily environment & support they need, sponsors, developers, and users throughout the project. and trust them to get the job done. should be able to maintain a constant pace indefinitely.

07 Working software is 08 The most efficient and effective 09 Continuous attention to technical the primary measure of method of Conveying information excellence and good design progress. to and within a development team enhances agility. is face-to-face conversation.

10 Simplify--the art of 11 The best architectures, 12 At regular intervals, the team maximizing the requirements & designs reflects on how to become more amount of work not emerge from self-organizing effective, then tunes and adjusts its done--is essential. teams. behavior accordingly. Agile Is a Methodology Only

There are several agile project management frameworks being successfully used for delivering Drupal projects. Let’s evaluate few popular agile frameworks:

1. Scrum 2. Kanban 3. Scrumban AGILE 4. Extreme Programming 5. Lean Development 6. Feature driven development Scrum Lean In next few slides we will discuss each frameworks Extreme Kanban one by one and Help you choose the most fitting Programming for your projects. (XP) FDD Scrum

Scrum is an Agile framework that brings order to chaos.

Scrum comes from Rugby:

An ordered formation of players usedThe to cross restart functioning play team Sprint inAn which ordered the forwardsformation of of a players, team form used up to with restart arms play, interlocked in which the forwards of a team form up with arms interlocked and heads down, and push forwardPO, SM against & a andsimilar heads group down, fromand Nothe pushdistractionsopposing forward side. the team againstScrum adoesn’t similar work group when from the the team opposing is not side. working to a shared goal Scrum in a Nutshell

Processes & Tools The Team The project requirements

● Sessions ● Clear vision of the end Product Owner, Scrummaster and ○ Scrum Meeting (daily) product ○ Backlog Refinement Team ● A clear set of requirements grooming (1 or 2 per (user stories) Sprint) ● Well-trained ○ Product Backlog at ○ Sprint planning 1 or 2 ● Specialized least for the upcoming per Sprint) ● Capable of Self-management 2 sprints ○ Demo or Review (end ● Communicative of Sprint) ● Ability to Make Decisions ● Objective to add small ○ Retrospective (end of ● Common Goal marketable values in each Sprint) ● Self Improving increment ○ PSP: potentially ● Product Backlog shippable product ● Tools ○ MMF: minimal ○ Scrum Board marketable feature ○ User Stories ○ Burn Down Chart ○ Timeboxing ○ Icebox When to choose Scrum

Tools: Team: Output: ● A clear vision of the end ● The WHOLE scrum team is ● Something to show at the product onboard and committed end of the sprint ● Stakeholders have the ○ There needs to be enough of a product project as a priority—not necessarily a top priority, but ● The team gets a full sprint to backlog for a few sprints available for answers produce value without any (2-3) ● Team is focused: don't get interruptions ■ There can be many interruptions from changes but the everyday business ● Anything after that may be team shouldn’t ● The team is fully skilled team subject to change, this is where a sprint really lives up stop working to to match the project to its name adapt to change ● The team has the ability to

○ Scrum projects can communicate frequently and easily (daily stand ups, etc.) change direction as long as the product backlog is maintained and groomed When should Scrum turn to Kanban and Scrumban

● Sprint scope frequently changed due to “high priority”/ emergency situations ● Scope isn’t clear or is blocked ● Basic Scrum rules not fully enforce ● Releases start to be ad hoc ● No clear distinction between Project and Product ● Addressing maintenance and support work as main sprint goal ● Team dedication is erratic KANBAN

Kanban is a visual signal that's used to trigger an action. The word kanban is Japanese and roughly translated means: “card you can see.” Toyota introduced and refined the use of kanban in a relay system to standardize the flow of parts in their just-in-time (JIT) production lines in the 1950s.

"Kanban promotes flow and reduced cycle-time by limiting WIP and pulling value through in a visible manner." -Torbjörn Gyllebring KanBan in a Nutshell

Processes & Tools The Team The project philosophy

● Sessions ● Kanban doesn’t prohibit ○ Meeting (daily) ● Technical needs as per change, but it doesn’t ■ Often those that have requirement of the prescribe it either. converted from Scrum to Kanban,are inclined project to keep the daily ● Kanban encourages stand-up Kanban recognizes that there making incremental ● Product Backlog may be value in the existing changes to avoid drastic ○ Team to pull the tickets process, roles and decrease in productivity ● Tools responsibilities ○ Kanban board ● Small course corrections ○ WIP limits Take what is working and are also just easier than ■ Limiting the amount of altering the complete WIP, at each step in the preserve it. process, prevents process overproduction and reveals bottlenecks ● Vision of the end product dynamically so that you can address them before they get out of hand. When to choose Kanban

● Operation support ○ Running a production system as a whole, Focus ● Maintenance work and support projects ● Continuous flow ○ No nee0d to stop to reassess just keep on going and deploying Courage ● When the project requires the maximum flexibility and frequent change of priorities and scope ○ When the goals are not clearly defined Openness ○ Risk of scope creep ● Ad hoc releases required Respect ● Team dedication is erratic ○ When team isn’t focused - responsibilities elsewhere. ● If management isn’t ‘into scrum’ Commitment ○ Management isn’t giving the needed time and attention to the project SCRUMBAN

Mix of scrum and Kanban

Scrumban is a management framework that emerges when teams employ Scrum as their chosen way of working to Scrum + Kanban = Scrumban understand and continuously improve how they work and use the Kanban Method as a lens through which to view (kanban board)

● Scrumban comes into play to help teams with the transition from Scrum to Kanban. Can stay here a while ● ● Scrum-ban is still unclear. Is it an improved Scrum or and improved Kanban ● Scrumban is not unique to the software development process ScrumBan in a Nutshell

Processes & Tools The Team The project philosophy

● Sessions (The Scrum) Improvement on; ● Stand up for daily check in Like Scrum ● Roles ● Retro for team ● Cross functional ● Work processes improvement ● Better flows ● Review- for incremental ● Allowing for specialized releases to demo to the teams and functions ● Flexibility client ● Dedicated team ● Product Backlog

● Tools (The Ban) ○ Kanban board ○ Ad hoc release ○ Continuous flow ○ WIP limits ○ Pulling tickets ○ Grooming on demand When to choose Scrumban

● Any Scrum with an unstable and/or moving vision ○ When the project requires the maximum flexibility and frequent change of priorities and scope ○ When the goals are not clearly defined ○ Constantly evolving product ○ Sprint planning isn’t happening

● If management isn’t ‘into scrum’ ○ Management isn’t giving the needed time and attention to the project

● Any Kanban project that needs the structure of Scrum ○ Hard deadline ■ Still working to the objective ○ Team not focused Extreme Programming (XP)

Extreme Programming (XP) is another agile development framework, focussed on improving software quality and responsiveness to evolving client requirements. Extreme programming advocates frequent releases in short development cycles in order to improve productivity and introduce checkpoints so that new requirements can be accommodated.

Planning Game Simple Design Pair Programming On–site Customer Small Releases Testing Integration 40–Hour Work Week Metaphor Refactoring Collective Ownership Coding Standards

Other elements of extreme programming are: programming in pairs, code reviews, unit testing of all codes, avoiding programming of features—until they are actually needed, a flat management structure, simplicity, and clarity in code. Extreme Programming XP (Prabhat )

Simple design Spike solutions ● Extreme programming is CRC cards prototypes code first approach to software delivery and User stories values Design emphasizes on four basic acceptance test activities: coding, testing, criteria iteration plan listening, designing. Refactoring

● Extreme programming Planning brought testing at the Coding forefront of the delivery process which helped with Pair Programming evolution of core software engineering. Testing Unit Test ● Practices like: automated Acceptance Testing Continuous Release testing, refactoring, Integration continuous integration, Software and test driven Development Project velocity development. computed Advantages & Disadvantages of Extreme Programming

Advantages Disadvantages

● Pair programming under XP helps in Detailed planning is required right since the writing better codes inception of XP due to changing scope and ● Increased team accountability associated cost ● Extreme Programming manages risks in a better way ● XP does not have a set measurement plan ● Source code is always robust as simplicity or quality assurance for coding. helps in faster development and less ● Pair programming may lead to too much defects duplication of codes and data. ● Easy to accommodate changes ● XP is more code centric than design which may cause UI/UX issues in larger projects. XP in a Nutshell

Processes & Tools The Team The project philosophy

● Pair programming Team Size - 5 or less ● Code first ■ Planning game ● Tracker, Customer, ● Refactoring ● Release Plan Programmer, Tester, ● Simple designs ■ Iteration plan Coach ● Project velocity ● Well-trained ● Spike solutions ● Specialized ● Iteration - Usually 1 week ● Co-located long

Practices

● Test driven development ● Continuous Integration ● Collective code ownership When to use XP

When to use Maturity ● Have reached a certain level of maturity as usual tasks, defects

and smaller unrelated user stories Flexibility

● Require maximum flexibility and frequent change of priorities Unscheduled ● Have multiple releases per week or per day Releases ● Have many unscheduled releases

● Have less cross functional teams Less cross functional team Lean Development

● Lean was adopted for the software industry in the year 2000 Cost Revenue Problem Solutions Key Metrics Structure Stream ● Later on lean was applied for startups in a book “Lean Startups” by Eric Reis as a way of developing new product and services in circumstances of extreme uncertainty.

Channel ● A typical lean process: Learn-Measure-Build cycle, Advantage performs quality analysis, and testing, frequently connects with clients to understand the business value and focuses on continuous improvement

● The continuous cycle leads to sustainability, smart development, and success Advantages and Disadvantages of LEAN

Advantages Disadvantages

● Complements existing practices. ● Does not specify technical practices. ● Focuses on project ROI. ● Requires constant gathering of metrics ● Eliminates all project waste. which may be difficult for some ● Cross-functional teams. environments to accommodate. ● Theory of Constraints can be a complex and difficult aspect to adopt. Lean in a Nutshell

Processes and Tools The Team Key Principles

● Sessions 1. Eliminate Waste ● Well-trained ○ Daily Stand up 2. Build Quality “in” ● Specialized meetings 3. Create Knowledge ● capable of ○ Operations Review 4. Defer Commitment self-management 5. Deliver Fast ● Communicative ● Tools 6. Respect People ● Ability to make decisions ○ Cumulative Flow 7. Optimize the Whole Diagrams ○ Visual Controls ○ Virtual Kanban Systems

● Iterations ○ Small Batch sizes ○ Automation Feature Driven Development

● Feature Driven Development is a pragmatic software process which is architecture centric and focused to achieve the goal of client.

● Feature Driven Development was introduced in 1999 in a book named “Java modeling in color with UML.”

● As the name suggests, features are an important aspect of FDD. These are the primary source of requirements and primary input into the planning efforts in FDD.

● A feature is a small, client-valued function expressed in the form: