Telerik blogs
  • Productivity Testing

    How We Test Software: Chapter Four—Telerik Developer Tools

    Have you wondered how the teams working on Telerik products test software? In the next chapter of our detailed guide, we give you deeper insight into the processes of our Dev Tools division.
    November 29, 2016
  • Productivity Testing

    Quality and Testing Trends in the Digital Transformation Era

    Quality and Testing Trends in the Digital Transformation Era 870x220
    Quality Assurance & Testing fulfills a critical role in any digital transformation journey. Identifying the right tools, methodologies and measures to assure customer experience is increasingly essential to success.
  • Productivity Testing

    6 Key Steps to Successful Agile Testing Projects

    Application teams are continuously adopting agile software techniques as the principal method of building applications. Agile methodologies, such as Scrum, Extreme Programming, Feature-Driven Development and Test-Driven Development offer the ability to iteratively develop applications.
    February 13, 2015
  • Productivity

    Two Agile Myths- BUSTED!

    Agile is just a series of waterfalls There’s a lot more to being agile than just shortening the cycle. The waterfall process is defined by stages (or tollgates) that happen in serial - Requirements, Design, Construction, Verification, and then Maintenance. Agile incorporates all of these tasks in parallel, with a focus on collaboration, rapid feedback loops and the embracing of change. Each story (or item of value) moving through an agile queue can be labeled with similar states from waterfall. This does not make the sprint mini-waterfalls. Since the transitions are at the feature/story level (and not at the project ...
    November 22, 2013
  • Productivity

    Personas- Who Are You Building Those Features For?

    All people are different. In bazillion ways. Some are young, some – old. Highly educated or just in pre-school. Some like cats, others like dogs. Some have an iPhone, others use an Android phone. When we build software we most often build it for someone else to use. And the people that use that software are different from us. They know different things, they expect different things, and they like different things. So you cannot possibly expect that when you build a feature, everyone will know how or why to use it. If you bet on a wrong design people ...
    November 11, 2013