Skip to content
This repository has been archived by the owner on Sep 4, 2019. It is now read-only.
Matt Costanzo edited this page May 3, 2013 · 16 revisions

What is the BlackBerry Native Plug-in for Microsoft Visual Studio?

The BlackBerry Native Plug-in for Microsoft Visual Studio integrates with your Microsoft Visual Studio development environment. You can use the BlackBerry Native Plug-in for Microsoft Visual Studio to develop C and C++ applications that target the BlackBerry 10 OS and the BlackBerry PlayBook OS.

What is the purpose of this document?

The purpose of this document is to inform interested external parties about the processes of the Development, Testing, Contributor, and Product Management teams surrounding the release of software and issue fixes for the BlackBerry Native Plug-in for Microsoft Visual Studio.

Prior to reading this document, it is assumed that the reader:

  • Is familiar with programming C, C++, and C# applications
  • Is using BlackBerry 10 Native SDK or BlackBerry Native SDK for Tablet OS
  • Is familiar with GitHub
  • Can build their own project from GitHub
  • Understands the agile process

Role definition for BlackBerry Native Plug-in for Microsoft Visual Studio

  • Development: The team responsible for implementing requirements as defined by Product and Project Management and responsible for issue fixes
  • Contributor: An external 3rd party who may contribute a fix to an issue or a new feature. These fixes/features will not be integrated until reviewed by the Development team.
  • Test Team: The team responsible for testing official builds and verifying that issues have been fixed
  • Product Management: The group responsible for creating the roadmap for the project and assigning priority to issues and user stories
  • Issue Originator: The person who logs an issue

Service Level Agreement

The Development team will ensure that any inquiries submitted will be acknowledged within 7-10 business days.

Agile planning in the context of this project

Agile planning allows a software team to prepare for the unpredictability surrounding the goal of software development. In terms of planning, there are short work sequences known as sprints. The Development team holds weekly sprint planning meetings that fall on a Friday. A sprint lasts one week and begins and ends on Saturdays. Sprints are denoted by the end date of the sprint and are also given a numeric value, starting from Sprint 1.


Clone this wiki locally