Sprint Planning [Sprint Meeting] What is a Sprint? A Sprint is a set period of time during which specific work has to be completed and made ready for the review. Typically, a sprint is about 2 weeks long and the stories/tasks taken for that period should be completed with in that time. Let us know certain things before going further in our discussion like product backlog , sprint backlog, sprint dashboard, stories, tasks, story points, backlog grooming, backlog refinement meeting etc. A story can be a small thing like adding a button, a user to the system, discussing with the client etc. A task can be little more than a story that requires more effort like creating a basic login for the website, changing the database model to some extent, making calls to get new customers etc. Product Backlog: You can create as many stories/ tasks/ issues you can to deliver the product according to the requirements. In this backlog, all the stories/ta...
Posts
Storage Mechanisms [Common Terms]: Local Storage: With local storage, data can be locally stored without effecting the browser's performance. It is secure and the user can store large amounts of data unlike cookies. No expiration to the data that is being stored. Even if the browser is closed the data is not deleted. Session Storage: Local and session storage are same when it comes to their storage capability. But the later, stores the data only until the session is available. It deletes the data as soon as the session ends. Otherwise, when the browser is closed. Cookies: These carry some data from the server and are placed on the client computer. Cookies can also use your browsing history to change the search results. If you remember getting recommendations from the websites, that is because your interest is being cached and is used to generate that result. Important: One website, domain or protocol cannot use cookies, local storage or session stora...
Proxy Server? A server that acts as a middleman between the origin server and your application. [Wiki] A proxy server that acts as an intermediary for requests from clients seeking resources from other servers. Every request is sent to the proxy server. So where will the proxy server exactly be. By the definition, it resides in between the application and origin server. How does it work? All the requests are sent to the proxy server. This proxy server caches the objects. Only the new objects are requested from the origin server. It reduces the number of requests to the origin server and also increases the performance of the application. I hope this gives you a nice basic idea. Thanks. Happy 'Proxying' guys.