Twelve Principles of Agile Software

Following are the 12 principles of developing a software in an agile environment,

  1. A customer should be satisfied through early and continuous delivery of valuable software. So the first important objective is how you satisfy the customer in terms of delivering the valuable software.

  2. Any change in the requirement, even late in development, should be welcome. Agile process harness change for the customer's competitive advantage. Agile teams are adaptable to change and they welcome change.

  3. A proper working software should be delivered frequently, from a couple of weeks to a couple of months, with a preference to the shorter timescale. So the main objective is to deliver working software frequently probably in terms of few weeks or few months.

  4. Business team and developers must work together daily throughout the project. So it’s against a convention where business people are involved only in the initial stages and during the user acceptance testing so they are part of the team.

  5. Projects should be build around motivated individuals. Proper support and environment should be provided to the developers and motivate and trust them to get the job done in efficient way. So you talking about an agile team where team members have motivated themselves and they trust each other.

  6. The most efficient and effective method of conveying information to and within a development team is face-to-face conversation.

  7. Working software is the primary measure of progress

  8. Agile processes promote sustainable development, so business team, developers and users should be able to maintain a constant pace throughout the project. A sustainable development means where developers are able to sustain the pace in which they do the development.

  9. Continuous attention to technical excellence and good design enhances agility.

  10. Simplicity is essential. Too often methodologies, frameworks and process improvements get mired down in heavy process and documentation.  It’s a balancing act. It’s important to be neither too much, nor too little – just right. Basically simplicity refers to the tasks or activities which are only relevant to what is needed for the project or the project goals.

  11. The best architectures, requirements and designs come out from self-organizing teams. Self-organized teams are teams which are mature enough and self-directed, so don’t need to have autocratic way of working where all directions are given by the project manager (or any manager for that matter).

  12. The last principle of agile methodology is that, at regular intervals, the team reflects on how to become more effective and then tunes and adjusts its behavior accordingly. So whenever there are changes or whenever there are improvements which are identified by the team so team members adjust their working based on that and adjust their behavior accordingly.


Agile Manifesto's 12 Principles



Comments

Post a Comment

Popular posts from this blog

Data Bound Controls in ASP.Net - Part 4 (FormView and DetailsView controls)

FormView The FormView control is used to display a single record from a data source. It is similar to the DetailsView control, except it displays user-defined templates instead of row fields. Creating your own templates gives you greater flexibility in controlling how the data is displayed. The FormView control supports the following features: ·          Binding to data source controls, such as SqlDataSource and ObjectDataSource. ·          Built-in inserting, updating and deleting capabilities. ·          Built-in paging capabilities. ·          Programmatic access to the FormView object model to dynamically set properties, handle events, and so on. ·          Customizable appearance through user-defined templates, themes, and styles. Templates For the FormView control to display content, you need to create templates for the different parts of the control. Most templates are optional; however, you must create a template for the mode in which the control is configur
Read more

ASP.net: HttpHandlers

Image
HTTPHandlers: ASP.NET handles all the HTTP requests coming from the user and generates the appropriate response for it. ASP.NET framework knows how to process different kind of requests based on extension. For example, it can handle request for .aspx , .ascx and .txt files, etc. When it receives any request, it checks the extension to see if it can handle that request and performs some predefined steps to serve that request. ASP.NET provides a low-level request/response API that enables developers to use .NET Framework classes to service incoming HTTP requests.So as a developer, One might want to handle some new kind of requests such as requests for .jpg or .gif. ASP.NET provides HTTPHandler to handle requests for .jpg or .gif. An ASP.NET HTTP handler is the process or endpoint that runs in response to a request made to an ASP.NET Web application. The most common handler is an ASP.NET page handler that processes .aspx files. When users request an .aspx file, the requ
Read more

The Clickjacking attack and X-Frame-Options

Clickjacking  Clickjacking is a type of “web framing” or “UI redressing” attack. What that simply means in practice is that: 1. A user (victim) is shown an innocuous, but enticing web page (think watch online video) 2. Another web page (that generally does something important – think add friends on social network) is layered on top of the first page and set to be transparent 3. When the user thinks they are clicking on the web page they see (video), they are actually clicking on the higher layered (framed) page that is transparent There are two main ways to prevent clickjacking: 1.     Sending the proper X-Frame-Options HTTP response headers that instruct the browser to not allow framing from other domains 2.     Employing defensive code in the UI to ensure that the current frame is the most top level window Using X-Frame-Options X-Frame-Options  originally invented by Microsoft for IE8, but supported by a number of browsers, this idea might have more
Read more