Productivity

As you can imagine, we use a lot of our own products internally - all our teams use our Agile Project Management software, Team Pulse; Sitefinity uses our ASP.NET AJAX tools, ORM and RadControls for Silverlight and Test Studio for automated functional and regression testing; Test Studio uses ORM, RadControls for WPF - and this does not even begin to touch upon the collaboration and cross product use here at Telerik. Well - why not showcase this - why not show how well the Telerik suite of tools can work together to boost your teams productivity? We thought we would start ...

Similar to my previous post, I've made small example to illustrate how to use Telerik Reporting in Microsoft LightSwitch Beta 2. 1) Create new LightSwitch project and add new screen:  

April 2011 is the month of “Just*”.  Telerik is going to host three deep dive webinars on the Just suite of products.  Join Josh Holt for the JustCode webinar on April 13 for an hour dedicated to showing you all the awesome ways that JustCode can make your development a breeze. Josh will be joining myself on April 20th as we we take you through an hour of mocking with JustMock, starting with the features in the Free Edition and culminating with the full version. Lastly, join Chris Eargle for JustOneMoreThing  on April 27th.  I could tell you more, but I’m not allowed to! ...

If it is true that time is money and, once lost, can never be found again, it should be no surprise that the “work smarter, not harder” mantra has become the drumbeat that agile developers must march to. One pillar of project estimation is having a solid grasp of how long will a given task take, and how long to complete the entire project. Even for those who have a strong grasp of this concept, delivering truly accurate estimates can become a frustrating, time-consuming process that results in projections that are far off the mark. Why? Because falling prey to ...

See also: ·         Part I: How I started to use Scrum ·         Part II: Scrum, but ·         Part III:  Moving away from Scrum In Part I we looked at how I got into Agile and Scrum. In Part II we explored how Scrum failed to be flexible enough to fit into my unique process. In Part III we took a look at how I got introduced to Kanban, without even knowing it. Today we’ll take a quick look at what Kanban is. Kanban is a Japanese word that loosely translated means “signal card.”  Kanban’s underlying thesis is that by using signal cards at various points in the production process to indicate the amount of work...