It's basically like allotting a certain amount of time for a task, and working on that task in that period of time. This allotted time is called as timebox.

It comes under agile methodology. This technique can help to control schedule better and improve the results. With timeboxing, you can likewise be more mindful of how long you spent on a specific undertaking, to not try too hard.

Some benefits of time boxing are:

1. Increase in productivity: We know that agile is an iterative interaction and henceforth it is exceptionally powerful. Consequently, keeping time period for every occasion will propel the group and thus improves usefulness.

2. Prevents Feature Creep: Timeboxing will permit the group to work with their greatest potential to arrive at the objective. They will go with the time and subsequently won't add any highlights expecting it to add value.

3. Sense of responsibility: Timeboxing reminds the PO to focus on item accumulations. It additionally causes the SM to follow timetables during gatherings. Scrum system underlines every day stand up and hence adhering to that 15 minutes is significant. Thus timebox will keep each partner on toes to pursue the outcome.

Some tips to implement timeboxing for Agile planning:

1. You should initially allot uninterrupted alone time for finishing your undertaking. You can do this dependent on your abilities and experience.

2. Start the clock and don't take a gander at it until you complete the responsibility. In the wake of finishing actually take a look at the clock to know whether you have taken a more extended time than dispensed or the other way around. In light of this experience you would now be able to kick off the leftover errand.

3. Before long you keep an eye on the circumstance of your first undertaking whether or not you complete on schedule, don't consider it for your next task. Simply have some time off and begin your next task with a new brain.

4. Break the assignment into more modest lumps dependent on your capability to forestall getting demotivated. Continuously recall that your fulfillment is significant and nobody will screen you on your assignment.

Kanban term appeared utilizing the kinds of "visual card," "billboard," or "bulletin", "flagging framework" to demonstrate a work process that limits Work In Progress (WIP).

The core concept of Kanban is as follows:

1. Visualizing workflow: Split the whole work into characterized portions or states, envisioned as named sections on a divider. Compose every thing on a card and put in a section to demonstrate where the thing is in the work process.

2. Work In Progress limit (WIP limit): Assign unequivocal cutoff points to the number of things can be underway at every work process portion/state. i.e., Work in Progress (WIP) is restricted in every work process state.

3. Measuring lead time: Lead Time, otherwise called process duration is the normal opportunity to finish one thing. Measure the Lead Time and streamline the cycle to make the Lead Time as little and unsurprising as could really be expected.

4. Pull approach: Pull approach is utilized as and when an errand is finished in the Doing segment. One more card is pulled from the To Do segment

The Kanban board gives simple admittance to everybody engaged with the undertaking, works with correspondence as and when fundamental. Additionally, the advancement of the assignments are outwardly shown. Bottlenecks are noticeable when they happen.

Advantages of using Kanban methodology are:

1. Team empowerment: Team is permitted to accept choices as and when required and is permitted to by and large purpose bottlenecks. The group approaches all the relevant data and is ceaselessly in touch with the client.

2. Continuous deliveries: The group can zero in on work fulfillment as there are restricted prerequisites anytime of time. This attention on conveying worth to the client and eventually accentuation the entire venture.

It is the act of having two designers and one working machine so that both the people can join and team up to deal with one perspective. In this training, both the people have one console and a mouse. One software engineer should code, and the other developer is told to notice the code. He checks whether the code being composed is adept for the necessary undertaking. He likewise spells, really looks at it, and sorts out whether the composed code turns out badly some place and the subsequent stage. The coder's singular's assignment is to code as per the prerequisite, and he want not stress over the thing is being composed since the other developer is editing it. The jobs can be exchanged whenever; the driver turns into the eyewitness as well as the other way around.

Some advantages of Pair Programming are:

1. It is better than one: There are two shrewd personalities to deal with the issue. At the point when two individuals figure out on one issue all things considered, the issue is settled quicker than that of one individual dealing with one program.

2. Lesser coding mistakes: There is less possibility of slip-ups in light of the fact that another software engineer is taking a gander at whatever the other developer is doing. In this way, it brings about better code.

3. Better knowledge exchange: Pair writing computer programs is an extraordinary method for sharing information. Both the individual developers can talk and look for help whenever. It permits the software engineers to have an up close and personal communication since it can convey much preferable outcomes over exhausting internet based instructional exercises.

4. Enhanced interpersonal skills: Pair programming consistently brings about the advancement of incredible relational abilities. Working together on a solitary undertaking elevates both the developers to see the value in one another's basic beliefs, correspondences and advances collaboration.

The Lean methodology, additionally called the Minimum Viable Product (MVP) procedure, includes delivering an absolute minimum adaptation of an item on the lookout, learning client inclinations, likes, and aversions, and afterwards doing emphasis dependent on the criticism that dispense with broad pre-arranged determinations.

Principles of Lean are:

1. Define Value: Value is the thing that the client will pay for. It is central to find the real or idle requirements of the client. There are numerous strategies like meetings, overviews, segment data, and web investigation that can assist you with interpreting and find what clients see as important By utilizing these subjective and quantitative strategies you can uncover what clients need, how they need the item or administration to be conveyed, and the value that they manage.

2. Map Value Stream: Lean IT, similar to its lean assembling partner, includes a philosophy of significant worth transfer planning charting and dissecting administrations (value streams) into their part interaction steps and killing any means (or even whole worth streams) that don't convey value.

3. Create flow: After eliminating the losses from the worth stream, the accompanying activity is to guarantee that the progression of the excess advances run as expected without interferences or postponements. A few techniques for guaranteeing that esteem adding exercises stream flawlessly include: separating steps, reconfiguring the creation steps, evening out the responsibility, making cross-practical divisions, and preparing representatives to be multi-talented and versatile.

4. Establish Pull: The objective of a draw based framework is to restrict stock and work in process (WIP) things while guaranteeing that the imperative materials and data are accessible for a smooth progression of work. All in all, a draw based framework takes into consideration Just-in-time conveyance and assembling where items are made at the time that they are required and in the amounts required. Pull-based systems are continually produced using the necessities of the end customers.

5. Pursuit Perfection: This makes Lean reasoning and nonstop interaction improvement a piece of the authoritative culture. Each worker ought to endeavor towards flawlessness while conveying items dependent on the client needs. The organization ought to be a learning association and consistently track down ways of improving every single day

Some benefits of Lean IT are:

1. IT processes will turn out to be more proficient through the decrease or end of waste.

2. Employers will turn out to be more useful and roused.

3. Lead time will be diminished, which means clients will get their items quicker and the association will bring in cash quicker too.

4. Work processes will create less deformities and costs will be diminished.

5. Consumer loyalty will be expanded through better quality items and benefits and decreased lead time, in addition to other things.

Refrences for images :

Timeboxing: https://www.google.com/url?q=http%3A%2F%2Fwww.sprinttriathlontraining.org%2Flogistics%2Flimited-training-time-how-to-adjust-your-plan&sa=D

Kanban: https://www.google.com/url?q=https%3A%2F%2Fwww.wisdomjobs.com%2Fe-university%2Fkanban-tutorial-2659%2Fkanban-introduction-26934.html&sa=D

Pair Programming: https://www.google.com/url?q=http%3A%2F%2Fjathinsoftware.com%2Fservice%2Fweb-design-development&sa=D

Lean IT: https://www.google.com/url?q=https%3A%2F%2Fqcfi.in%2Flean-case-studies%2Flean-principles%2F&sa=D