LINQ in asp.net 3.5 & SQL SERVER

Again here after long time to sustain my blog; I might not find paper or pencil to persist this and of-course I don’t fault on my time.

While I decided this topic I thought to categorize this and enhance as phase. Before dig in to this topic I have carried out some methodology to avoid the boring sense.

So my phase would be with WHAT / HOW

Let me begin with WHAT and rest will be scripting almost immediately.


WHAT is LINQ?

Language Integrated Query (LINQ) is a component released within the .NET 3.5 Framework. It is one of the greatest features of .NET 3.5. It serves the purpose of querying objects.

LINQ comprises a series of operators, which are used to query, filter and project data in arrays, enumerable classes, relational databases and XML. In order to query data, the data needs to be encapsulated as an object. In case the data source is not an object, it first needs to be converted to an object in order for LINQ to query it.

LINQ has its own Query Processing Engine. The information returned by a LINQ query is a collection of in-memory object which may be enumerated.

LINQ has its own Query Processing Engine. The information returned by a LINQ query is a collection of in-memory object which may be enumerated.

The LINQ concept treats the data source as an Object, rather than a Database. So we may say, its an object that is queried. LINQ may query any type of data source, like:

• LINQ querying SQL (MS SQL Server supported).
• LINQ querying Datasets (Querying is possible on Datasets and DataTables)
• LINQ querying ORM Solution
• LINQ querying Objects (In-memory data may be queried)
• LINQ querying XML (Querying is possible on XML data source

LINQ supports querying to those objects that implement the IEnumerable Interface.

PS: Continuation subjects

LINQ in asp.net 3.5 & SQL SERVER – How to apply LINQ

Agile Scrum Methodology - Basic for new agiler.

Basic Scrum Vocabulary

Before being able to implement Scrum, it is essential to be familiar with some key words in the SCRUM vocabulary.

Sprint- a 15- 30 days focused effort moving the team toward fixed goals/output.

Product Backlog- a constantly prioritized to-do list (task & activities).

Sprint Backlog- a list of the highest prioritized items from the product backlog.

Scrum Master- the coach for the product management team and works to ensure the realization of the goals of the sprint.

Product Owner- represents the customer and is responsible for prioritizing the backlog.

Scrum Team- a group of 5-9 people who self-organize and have joint responsibility for the completed tasks.

The Scrum Process

Now that basic vocabulary related to Scrum has been defined and I will detail the Scrum process step-by-step.

1. Creating a backlog – in this step, the Product Owner and Scrum Team meet in order to discuss the priority and items on the Product Backlog. The Product Owner must be able to form the product vision. The Product Backlog then is a prioritized list of what is required for the project and is ranked with regard to importance.
2. Once the product manager creates the backlog, then there will be a Sprint Planning Meeting. During the first phase of the meeting, the Product Manager describes to the team the goals of the project and explains the Product Backlog. During the second phase, the Scrum Team will select the items to be completed during the sprint from those with highest priority on the Product Backlog.
3. Once the items to be worked on have been selected, a potential Sprint schedule is constructed – taking into account the availability of the team members to devote their time to the project. The items in the Product Backlog are assigned and broken down into individual tasks. Once this occurs, this document is the Sprint Backlog.
4. The Sprint begins and lasts from 15-30 days. During the Sprint, no other tasks are added to the backlog.
5. Daily Scrum begins when the sprint begins. The Daily Scrum is a 15 minute (Appropriate) stand-up meeting where each member of the team gives a very brief report to everyone else – what they accomplished since the last Daily Scrum, what they hope to accomplish, and issues that have come up. Here, the Scrum Master will make note of issues and attempt to resolve them – after the meeting.
6. Sprint Review – once the Sprint ends, everyone gets together in a meeting to share what he or she accomplished during the sprint.
7. The process begins again with a new list of prioritized tasks on the Product Backlog.

Further queries are welcome if anyone wants to know in-depth process in real-time scenario.

Start up IT company challenges.

There are few points to share regarding the challenges to be faced and the necessary developments required to start up IT firms successfully.

In this competitive world; small companies exist as small company and mostly remain that way..

What is lacking with these so called 'SMALL' Companies?
1. Lack of understanding the strength.
2. Lack of marketing in the subject matter and business plan.
3. Lack of appropriate financial projections.
4. Lack of focus on the targeted business development.
5. Ignorance of the process and documentation.
6. Incomplete requirement/scope freezing and communication among the team and the stakeholder.
7. Inappropriate Effort estimation and project plan.
8. Lack of the project management itself due to various constraints.

Rest; will be discussed in granular level in next posts...

Open topic on Agile Scrum.

Can we discuss here little bit about Agile Scrum methodology and its real time utilization. Lets assume that we are going to develop an Accounting Software for Product Seller. In this scenario the director wanna implement and maintain his accounts transaction and needs of basic reports what ever other firms are generating. Its basic starting point here; further am assuring that will come up with interesting topic to discuss and debate.