Latest
-
Productivity
The Importance of Prioritizing and Sizing Your Backlog for Agile Planning
Prioritized and Sized Backlog For agile planning to work, you must have a prioritized and sized (estimated) backlog. A prioritized backlog is simply a list of work that needs to get done that is ordered by priority. Essentially, the work at the top of the list is the most important and should be done first. In many cases, customers have a difficult time prioritizing lists of features, however, this makes the prioritized backlog even more important to produce. Another requirement of this backlog is that each of the items must be sized, which is another way of saying that the ...May 27, 2021 4 min read -
Productivity
3 plus 1 Awesome Features in TeamPulse You Probably Don’t Know About
In the last release we made some major improvements in TeamPulse so it can provide smoother experience on mobile devices. Now it’s even easier to track your work from your iPad or your smartphone. TeamPulse on your tablet We have done a lot of performance and UX improvements for mobile device. As a result you now got a faster board and list view, better search, quick add and activity stream, and more. While you would experience those for yourself, we wanted to share with you some tips and tricks on how to make your life easier when working with TeamPulse ...May 27, 2021 2 min read -
Productivity Testing
30 Days of TDD: Day Four – Making Your First Test Pass
In the previous post I discussed the tools I will be using in this series; Visual Studio 2013 Preview as my development environment, NUnit as my unit testing framework and JustCode as my test runner. I also introduced a requirement and wrote my first test to capture that basics of that requirement. In this post I’ll demonstrate one of the most important concepts about TDD by writing just enough code to make the first test pass. I’ll then add more tests to introduce more functionality to our library. -
Productivity Testing
How to Ensure You Are Doing Proper Acceptance Criteria Testing?
The importance of requirements Requirements are the lifeblood of the project. I need to establish first and foremost. Good, detailed requirements will carry the project team through to the end of a successful project more times than not. And that’s a good thing because more projects actually fail than succeed. However, weak or incomplete requirements will not – resulting in countless hours of rework, scope creep that can drive any project manager crazy trying to manage and maintain control over, and the potential for many change orders that will upset the most satisfied project customer quickly making them wish they had never brought their project needs to you in ... -
Productivity Testing
30 Days of TDD: Day Three – Your First Test
In this post I will introduce you to JustCode and the NUnit testing framework. I’ll also demonstrate the basic TDD workflow from introduction of the first requirement all the way through to writing your first test. At the end of this post you will have a test based on a given requirement. In the next post we will work through the rest of the workflow and make the test pass.
by 
by All articles
Topics
Web MobileMobile
Desktop
Design
Productivity
People
Most Popular
-
-
Web ASP.NET Core Productivity Reporting Integrating Telerik Reports with Your ASP.NET WebpageAugust 13, 2025
Latest Stories
in Your Inbox
Subscribe to be the first to get our expert-written articles and tutorials for developers!
All fields are required