This lesson will get you started with C# by introducing a few very simple programs. Here are the objectives of this lesson: Understand the basic structure of a C# program. Obtain a basic familiarization of what a "Namespace" is. Obtain ...
You've probably heard the word ASP.net fairly often these days, especially on developer sites and news. This article will explain what the fuss is all about. ASP.NET is not just the next version of ASP; it is the next era ...
A user story consists of ... Card Conversation Confirmation Card: User stories are written on cards. The card does not contain all the information that makes up the requirement. Instead, the card has just enough text to identify the requirement, ...
We spend too much time complicating our lives by trying to do too much, too fast! There seems to never be enough time to do something correctly, but always enough time to do it over again! Given to complexity of ...
The goal of kanban is to increase the value of a production process. Kanban increases the feedback in production by limiting the amount of work in progress at any one time. Without the "safety" of inventory, troublesome process steps and ...
Kanban is a concept related to lean and just-in-time (JIT) production. According to Taiichi Ohno, the man credited with developing Just-in-time, kanban is one means through which JIT is achieved. The need to maintain a high rate of improvements led ...
The weekly, bi-weekly or monthly "show-and-tell" is one of the customer's most powerful weapons. As a customer, you're holding most of the planning cards, too. If you choose to change the plan based on feedback every sprint, identifying new requirements ...
Evolutionary Design (XP) advocates evolutionary design methods in the place of planned design. Extreme Programming (XP) rejects significant effort in up-front design, in favor of a more evolutionary approach. Evolutionary design means that the design of the system grows as ...
In the "old" waterfall method of development, there are explicit milestones: first you develop requirements, then you create a design that meets those requirements, then you lay out the functionality that will implement that design, etc. Jeff Patton writes a ...
Story points are better than hours for estimaing because: We are bad at estimating hours, but more consistent with points Hours tell us nothing since the best developer on the team may be multiple times faster than the worst It ...
SCRUM helps you to ship running, tested software every two weeks or every month. SCRUM helps you review how your project is going and make frequent adjustments that help you achieve the goal of shipping tested, useful software. SCRUM allows ...
The difficulty in software development is not writing code or applying a certain technology stack. Instead, the challenge lies in the specification and design of the software itself. Therein lies the essential complexity of software development, an idea introduced by ...
Agile processes are designed to help you deliver what your customer actually needs, not what was originally asked for. In Scrum, you estimate a collection of user stories – in story points that represent complexity, and you predict how many ...
The cost of software development (changing existing features or adding new features) gets exponentially higher as a project progresses. Agile software development does not allow the efforts to spiral toward the inconceivable, unpredictable, and unmanageable end by keeping the effort ...
Learn the necessary technology skills iwhile accomplishing some real work. The initial backlog really only needs to be one item in order to start delivering. Learn the parts that aid building the system, rather than developing the system according to ...
If your project is small, simple and low-risk then the overhead of an Agile Project may not be worth it. Because of the planning (daily, iteration, release, project) and processes that Agile frameworks require, be sure your project is risky ...
Scrum and XP differ from other frameworks in the use of a burn down chart rather than milestones to measure progress. A product burn down chart tracks the amount of work, features or requirements that is still remaining. At the ...
Serial lifecycles, characterized by waterfall and Agile lifecycles, characterized by Scrum are not the only two choices when it comes to software development life cycles (SDLC). There are several more lifecycles from serial to iterative, incremental, and iterative/incremental. What Is ...
While Agile development does not guarantee business breakthroughs, it removes the development process as a risk and also helps with delivering a better user experience! Here are seven (7) principles that help define agile software development: 1. Short software development ...
The Waterfall software development model was formally introduced in a paper published by Winston Royce in 1970. Winston Royce introduced Waterfall as a flawed method of software development, that is vulnerable due to some shortcomings. Waterfall is a sequentially structured ...
According to the National Institute of Standards and Technology Manufacturing Extensions Partnership’s Lean Network, Lean is: 1. A systematic approach to identifying and eliminating waste through continuous improvement, flowing the product at the pull of the customer in pursuit of ...
Self organizing teams is one of the core concepts of Scrum and it makes Scrum unique compared to other methods / frameworks. Scrum emphasizes teamwork and self organizing high skilled workers. Some of the tenets of scrum include: 1. The ...
This book provides guidance for building cross-browser web applications with rich interactivity, a responsive user interface (UI), an immersive and engaging user experience (UX). The best standards for web development including HTML5, CSS3, and ECMAScript version 5, jQuery and ASP.NET ...
Thirty-five percent of developers surveyed by Forrester in late 2009 said they were using agile development. 31 percent said they don't follow a software methodology at all meaning they may use concepts taken from multiple development methods. The pros of ...
The 10 Key Principles of Agile Software Development: 1. Active user involvement is imperative 2. The team must be empowered to make decisions 3. Requirements evolve but the timescale is fixed 4. Capture requirements at a high level; lightweight & ...
