Skip to main content

Principles behind the Agile Manifesto

Recently read about agile manifesto. So thought to sharing it. More stories can be found at the agile manifest website, that is at the end.

1-   Our highest priority is to satisfy the customer through early and continuous delivery of valuable software.

2-   Welcome changing requirements, even late in development. Agile processes harness change for the customer's competitive advantage.
3-   Deliver working software frequently, from a couple of weeks to a couple of months, with a
preference to the shorter timescale.
4-   Business people and developers must work together daily throughout the project.
5-   Build projects around motivated individuals. Give them the environment and support they need,
  and trust them to get the job done.
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. The sponsors, developers, and users should be able to maintain a constant pace indefinitely.
9-   Continuous attention to technical excellence and good design enhances agility.
10-Simplicity--the art of maximizing the amount of work not done--is essential.
11- The best architectures, requirements, and designs emerge from self-organizing teams.
12- At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly.

 Reference:- http://agilemanifesto.org/

Comments

Post a Comment

Popular posts from this blog

Compiled Query- Improve the performance of Linq to Entity Query

Most of the small or medium IT firms are using the Entity framework for the Data Access layer (DAL). If we write a complex linq to Entity queries performance will always be an issue. But with the Compiled Query Performance can be improved. This below definitions are from MSDN and more details can be found on the MSDN Link that is at the end of this post           When you have an application that executes structurally similar queries many times in the Entity Framework, you can frequently increase performance by compiling the query one time and executing it several times with different parameters. For example, an application might have to retrieve all the QuoteRevision for a particular quotelineStatus, the quotelinestatus is specified at runtime. LINQ to Entities supports using compiled queries for this purpose.               The  compiled query class provides compilation and caching of queries for reuse . Co...
1 comment
Read more

Sql Server Internals - Named Pipes

Named pipes enables clients applications to request a reliable and two way connection between the client application and Sql Server, across a network. A named pipe has a name which follows the UNC naming convention : \\Server\pipe\name The default names pipe for SQL server is :                 \\Server\pipe\sql\query A named instance would have a named pipe of                \\server\pipe\MSSQL$instancename\sql\query Early versions of SQL Server only provided Named Pipes. Named Pipes also allows for impersonation of a clients credentials. The feature is used by SQL server when using Linked Servers. The clients logon credentials are passed across to the Linked Server for authentication. Named Pipes can operate over TCP/IP, NETBEUI or IPX as it indirectly relies on the Common Internet Files Sytems
Post a Comment
Read more

How to add a stored procedure in Entity Framework

Step1- Open the . edmx file Step2- Right click in . edmx file and select Update Model from Database Step3- Select Add tab, select Stored Procedures and select the procedure you want to add and click finish as shown in below figure a Step4- Build the Entity Project to make sure nothing is broke Step5- Right click on . edmx file and  select Model Browser Step6- Model Browser Popup will appear as  below figure. Click on the Strored Procedures in PricingToolModel . Stroe and click the newly added SP (it will appear here) Step7- The Add Function Import screen will appear Based on the return we can set up. If you are returning a multiple column Click on the Get Column Information First, then click the new Complex Type. After that you can  see the Return of Collection will select the Complex and a complex type is generated by EF If its returning scalar you can select which return type like int , string etc... If its return  entitty ...
Post a Comment
Read more