Posts in Distributed development

Loss The Documents and Spreadsheets (White Paper)

November 8th, 2014 Posted by Distributed development, Requirements Management 0 thoughts on “Loss The Documents and Spreadsheets (White Paper)”

Manage all ALM requirements types efficiently and more accurately with Orcanos QPack Requirements Next Generation tools. By Rami Azulay VP Marketing and Sales at Orcanos.

 

Introduction

It is well known by now that poor requirements management is among the most affecting contributing factors in the failure of a project. Misleading requirements management can put your organizational compas on the wrong direction and lead to unfocused teams, rework time, regulation violations, out-of-control costs and unhappy customers. If you use documents, spreadsheets, emails, homegrown tools and other tools to keep track of your business, customer or product requirements, you could be starting on the wrong foot and put your project at risk. Have you ever forgotten to notify all the people that needed to know about an update? And if you did notify, how sure your are that it was well understood? Have you ever been seeking for the correct version of a document before going into Design Review (DR) meeting? How much time are you spending on getting everyone comments into single document or had to take time to listen to people who were giving the same feedback?

 

This is a fact, Managing requirements is difficult with conventional office and productivity tools because they lack some key capabilities. It is not enough that we have a way to describe the requirement over and text editor a successful requirements management should also includes the ability to capture relationships between requirements that are part of the traceability requirements by any quality standard such as ISO 9001 or IEC 62304 or ISO 13485 and manage dependencies. For example, based on the level of concern related to your product there are level of depth required by the traceability used in your documents, you should be able to show how features that are being built relate to capabilities that customers have requested.

When different time zones are involved in your project that may bring another level of complexity to the communication on requirements. Each change requires a full audit trace according to the CFR 21 Part 11 if you are under such regulation restriction so that by itself will force you to maintain an history audit change on every change made to the document, never ending work and in some cases the that part of the document could be as big as the spec itself, so handling versioning and change management is crucial. When you try to manage requirements without these capabilities, the results can be low productivity, latency at project timeline and increase in costs. Using typical productivity tools, to manage requirements is like using a hammer to open a bottle. It gets the job done, but at what cost?

 

On the other hand, Orcanos© QPack Requirements™ Next Generation offers effective requirements management capabilities.

 

After 10 years in the market we can tell that these capabilities have helped Orcanos clients:

  • Reduce development costs by 52 percent.

  • Accelerate the time to market by 25 percent.

  • Reduce cost of quality by 62 percent.

 

This paper identifies five key benefits of the requirements management capabilities provided by  QPack Requirements™ NG that address what cannot be done with documents, emails and spreadsheets. These capabilities include requirements capture, online chat discussions, sharing, elaboration and management. Another key capability is collaboration between teams, whether they are local or globally distributed.

 

The benefits are:

  • Clear Understanding of a change

  • Consistency in development

  • Full V&V Traceability

  • Online – Real Time collaboration

  • Pro Active Alerts making your data work for you

 

Orcanos Software

With QPack Requirements™ NG your teams can collaborate more easily. After a document is ready for interested parties to review, stakeholders can use QPack Requirements™ NG to discuss and collaborate by commenting directly in the preview mode document. Important decisions can be finalized using the work item workflow and discussions are being logged by the chat feature available to the team. Now you can stop chasing down emails or making, consolidating and responding to similar comments, saving all that common wasted time. With  QPack Requirements™ NG, chat comments can be directed to team members and classified as private or public to avoid unnecessary noise between stakeholders, so the important things can be handled directly by the right person. As people make comments, QPack Requirements™ NG can send SMART email notifications, including a recent history change log as well hyperlink that enables users access to just the information they need. Review cycles are shortened and collaboration is improved even when different time zones are involved. Keeping stakeholders informed and engaged is critical. With QPack Requirements™ NG, the flexible notification mechanism can identify the team automatically and keep them in the loop of changes. Along with email notifications, QPack Requirements™ NG has improved dashboards so users exposed to  the most important information as soon as they log in to this pure HTML5 web-based application. Dashboards can have presentation of endless data dimensions, project timelines, changes that have been made in the scope of the change itself of the document that the change was discovered in along with any ongoing reviews and comments.  QPack Requirements™ NG acts as an “Absolute source of facts” and enables interested parties to access the latest information automatically. Customers don’t lie Orcanos clients have used  QPack Requirements™ NG software to reduce development costs by 52 percent and costs of quality by 62 percent, while accelerating the time to market by 25 percent.

 

Benefit 1: Live collaboration over documents, spreadsheets or email can cause never ending  headaches when you work with others, distance can be as short as working on the same building, and especially if you are part of a globally distributed team. Most vendors of requirement management tools will create what we call “information islands” that make it difficult to find, relate and use this information. Colleges spend too much time searching for the latest information, reviewing documents and consolidating changes. In many cases you might think you have the most up-to-date information data, unmeasured lost of time gathering everyone inputs, reviewing and combining it. As a result, requirements might be weeks out of date from the point where it started as business idea to the finish line when it is delivered. With productivity tools such as office and excel, multi-user editing is difficult and almost impossible to manage. Consequently, several versions of the document might circulate throughout the team. For that Orcanos not just giving you Next Generation tools but also accommodate them with complementary tools that will allow you to make the working habits much easier, that comes with QPack DMS™. The owners of these documents must consolidate changes, maintain an updated copy and inform teams about the changes using QPack DMS as centralized tool that both meet the regulation standard ISO 13485 sec. 4.2 as well give simple easy to adopt tool, can do all that work for you.  QPack Requirements™ NG, by contrast, offers automated requirements freezing mechanism. By that more than one person can work at the same time on the same information and collaborate wherever they are located. The latest information is available for the team to access via the web or mobile application coming all from the same house of vendor Orcanos.

 

Since you never rest assure that you are all in sync, team members undertake heroic measures to consolidate, understand and monitor status of their requirement. Then, decision is taken based on this information. Unfortunately, if the data is error prone, it cannot be trusted and the project is put at risk. With QPack Requirements™ NG, each member of the team can access the latest information when he needs it. The template format of the original document is preserved. If required, for each traceable requirement working item annotations, such as priority, risk, status and category, can be displayed in grid report. The contents and chant annotations can be searched, sorted and filtered. You can also save views, which enables you to do MASS change on the perspective of your data quickly and display just the  information you need. Drill down analysis is quicker and the presented data used by you is more consistent and accurate.

 

Benefit 2: Getting Project data in consistency can be very complex. Teams members have a need for filtering relevant information and to organize it in logical manner. With  QPack Requirements™ NG, a project admin can set up different templates for each unique type of document such as MRD, PRD, SysRS, SRS, SDD, STP, STD, STR, Risk etc. That outline templated can be the basic structure of the information to be placed into the documents using traceable items. For example, a system requirements template can include boilerplate text for the introduction and areas for functional and nonfunctional requirements. In addition, each

work item type of can be “templated” with the appropriate annotations that must be collected by the author of that particular work item. For example, system requirements are kept in a product requirements specification that includes all related product components annotations, such as cost, risk or priority, along with any additional information they might need. On the other hand looking back on traditional document tools, it is not possible annotate requirements specifications without adversely affecting the original structure and context. In addition sorting or filtering documents based on any type of information and determining which requirements are missing is not possible. At the end of the day, someone must clean up the documents and remove the annotations in a very precautions way. Then once you got the document finalize the common practice of word processing users is often to copy the requirements from their documents into spreadsheets (keeping some level of traceability) and then adding separate columns to filter by them. When the documents are updated, the users must manually synchronize the changes for all documents and spreadsheets. These manual processes are often time consuming, they don’t scale and they can introduce errors into the process.

 

Relationships between artifacts can be displayed in columns, along with the requirements and annotations, which increases the visibility on the project status. As an outcome you improved quality and better project management. Filters can be saved and broadcast via proactive alerts, which enables the team or single member which is assigned to a task to once again quickly change the perspective of the data to fit the needs of the stakeholder.

 

The real value of traceability provided by QPack Requirements™ NG is evident when a project team must respond to an audit request by any notify body or must understand the impact of a change on existing features. If you use spreadsheet you may struggle to maintain the traceability and later interpret the connections between different levels of requirements that are found in multiple documents and are related by yet another document in the form of a spreadsheet, and that can go on and on. The guidance regarding the compliance of the project activities to user requirements or assessing the impact of change becomes challenging and uncomfort. With QPack Requirements™ NG, these challenges are avoided and almost does not exist. You can record multiple relationships with many to many ratio as you see them and use rich analysis tool to view details about the related work item from your actual current preview document without having the need to navigate away. When necessary, the relationships are traversable, which enables teams to quickly navigate from one document tree to the other. You can split your screen to create the traceability between 2 documents and use the multi selection tree view mode to perform faster. The way QPack Requirements™ NG display related information in columns can highlight the gaps and find inconsistency in the document whereby user requirements were left orphaned or are missing downstream interpretation to lower level requirements or upstream to final product. Such Pre-Audit alerts which can be built into your organization process, does not leave the worst for last and just let you handle it when something needs your attention. They can help identify scope creep, whereby functionality missing project goals or business needs as described by the marketing people, which uses up valuable time. Because you can see the requirements and multiple levels of relationships graphically, you can more easily and quickly assess the impact of change. And, during design reviews (DR) when required, you can demonstrate what is needed also during an audit without having to search for multiple documents and team members. Knowledge is being preserved throughout the years and not dependency exist over people who left you company. Traceability in QPack Requirements™ NG is dynamic. As soon as someone else makes changes in the tool, an update is immediately created. If a downstream requirement changes, it automatically shows up in traceability columns for the upstream requirements. Users have access to an up-to-date traceability matrix whenever it is needed and can also see what impact the change has.

 

Benefit 3: The use of spreadsheets for traceability are often used to add an additional dimension to requirements documents by storing needed annotations. Additional spreadsheets are used to capture relationships for the V&V, between requirements and tests. Verification matrixes,

compliance matrixes and traceability matrixes then must be maintained separately. These manual processes do not scale and are prone to user errors. In  QPack Requirements™ NG, users can “trace as they think.” Even they can start the relations from the QPack Service Center™ They can create relationships between new Service Call to the asset RISK which is required by the IEC 60601 requirements and respond to that RISK by mitigation proofed with traceability to the mitigation method.

 

QPack Requirements™ NG supports automation of the creation and maintenance of the relationships throughout the application lifecycle development. This includes relationships between requirements, work items, architecture, design and test plans. It removes the “air gaps” between “information islands” that are the result of using different tools. Removing these possible gaps reduces user errors.

 

Benefit 4: One of the unavoidable events in a normal project lifecycle will be the introduction of a change after project kick started, the effort understanding A change create turbulent period in a project once it comes after the initial requirements have been written and agreed on. At the PDR and CDR (Critical Design Review) All parties are happy and go on their merry way to work on the initial set of requirements. Than changes occur. Customers change needs to change their business strategy or replace low priority requirement with high priority requirement. A supplier is unable to meet an original target for cost or performance. An engineer or test reveals that what was planned is not possible. Or, more simply, a requirement already acted on developed and even test, is corrected. Managing changes as effectively as possible is imperative.

 

Before making a change it is recommended to follow those two main steps:

  • One, analyze the impact of the change before it is made

  • Second ensuring that all impacted areas have been revised as necessary

 

If you are using documents and spreadsheets above guidance can not easily achieved when spread over pieces of information. It become even worse If that information had to come from a failed test or reported a defect that was raised or if a client issues an updated specification, a document or spreadsheet cannot analyze the impact. That leaves the individual responsible personnel usually to spend weeks trying to understand the impact of change. With QPack Requirements™ NG, a user can create a perspective or view of their data. That view shows allows them to do drill down quickly to any direction they wish to follow. The user of V-Module when implemented makes that work even easier. In accordance to the V&V module each requirement should be trace down to the lowest implementation details design and even to the code if software was involved or engineering drawings and then from there to other steps of the development process, such as test. Users can also explore graphically the complex map of information that can be used to understand the impact of change that spans multiple levels and even components. This information is not static, using QPack Requirements™ NG you build your solution in a way that you can share features between several products so one change can affect more than one product. It can be updated as soon as someone else makes changes in the tool. If a downstream requirement changes, it automatically shows up so users can see what impact the change might have. Doing that with traditional tools huge effort will be placed to communicate these changes among everyone that is concerned and ensuring that all

impacted areas are addressed. From upper management to production floor all stakeholders and others want and can know what changed, how it changed and if they must act on the change. With QPack Requirements™ NG, a full history is maintained every time a requirement changes and that is also according to the CFR 21 Part 11 requirement for electronic records management. The team member can refer to the history and determine what changed, who changed it and when it changed and most important on what release it was changed. Change that was introduced into older release now needs to be observed twice: once into the older release and second to the new one. QPack Requirements™ NG also takes advantage of the relationships between information. Suspicion profiles alert users of a change with additional information regarding the actual document affected by the change. Users can review and act accordingly. This event will occur on every other change, a new suspicion is raised. With a minimum of effort, changes propagate down the levels of linked information in the project.

QPack Requirements™ NG helps your whole team assess the impact of change before it happen, using existing relationships and other meta data.

 

Benefit 5: In order to improve the ways your can look at your data you can limited doing that if you are using documents and spreadsheet. For example, you will need to present the data in different structure based on the audience intending to review it. Your customer might want their requirements structured as a document to simplify the review process. On the other hand, the looking at the same requirements from a finance perspective may required a table layout so they can estimate how much each requirement might cost. Using spreadsheets, these alternative perspectives on the same data require creating separate versions of documents. You must then maintain them or extract and consolidate them from a variety of sources every time reports are needed. QPack Requirements™ NG stores information in a central location and presents it in the format of a document. Users can add attributes to individual statements without changing the original structure, and they can filter and sort information based on the supporting characteristics. QPack Requirements™ NG automatically maintains cross references and relationships between information so you don’t have to. It also tracks change and alerts people of change that they might need to act on.

 

Best practices for writing clear, unambiguous requirements that can be tested can help reduce project complexity. To align all participants on the same terms used it is recommended  to include glossaries. With QPack Requirements™ NG, the glossary is accessed from a document. You can search or update terms and even update the glossary from the

document when they are introduced.

 

Conclusion

One of the most difficult decision about tool selection is to select the right tool for the job. It is organizational decision and not individual so you need the maturity to start going in that path. With QPack Requirements™ NG you can work smarter rather than harder. Putting the right people to view the right perspectives of the data for their roles at the right time. Avoid spending weeks to manipulate many documents and spreadsheets to see clear things in a way you want can be a practice of the past. Now you can spend time working on the more important details of your project, and let the tool relief from you time-consuming and repetitive tasks. QPack Requirements™ NG enables you to control your project. You can focus on important tasks, such as building and testing, without having to manually recording every change in multiple documents and spreadsheets. You can respond quickly and work faster with while increasing  traceability for better impact analysis. Notifications are automatic and immediate so your can respond with near real time to the point of the event. Now collaboration across locations can be assess before the change happens, to create a strategy for change and to act on a required change. Open the door to success. Orcanos QPack Requirements™ NG is your solution to a smarter project. Orcanos clients have used  QPack Requirements™ NG to enable effective requirements management that helped them reduce development costs and cost of quality, while accelerating the time to market. You could be next.

 

For more information

To learn more about Orcanos  QPack Requirements™ NG , contact your Orcanos representative or Orcanos Business Partner, or visit the following website: www.orcanos.com

 

© Copyright Orcanos Corporation 2014

Orcanos LTD

Practical tips for establishing distributed teams in QPack

October 22nd, 2014 Posted by ALM 2.0, Collaboration, Distributed development 0 thoughts on “Practical tips for establishing distributed teams in QPack”

This post describes the steps required for building your team

System Setup

Define workflows

Fro requirements, tasks, defects, etc.

Define work items layout

Build each work item layout – means the attributes for each work item

Define groups

Define the groups and groups permissions such as Project manager, Tester, Developer, etc.

Add QPack users

Now you need to add users to the system.

Define the chat permissions when adding user (allow private/public)

Relate users to groups

Relate users to groups. User can be related to several groups (for example, user can be related to Tester and Developer groups, in one project he can be a tester, in another project he can be developer)

Relate users to projects

Now relate users to projects using a specific group (user is connected to project via group)

Manage data sharing and settings

This allows more control of what to expose for each group or each project in terms of applications, modules, work items, fields, etc.

Build filters

For now, filters are added in QPack desktop. Add filters such as All items, My items, My open bugs, etc.

Define email notifications

You can build email templates based on events. Build email template for new bug, or for bug that is fixed and requires verification, all my tasks past due date, etc.

Build filters for end users and filters for managers

Define alerts

Based on the filter – define daily/weekly alerts to notify users on items they need to handle, such as tasks past due date, or open bugs waiting for me

Daily work with QPack collaborative environment

Now, that everything is setup and in place, how do we work on daily basis

The specific working methodology can be different from one company to the other, as one company manage system requirements, and the other doesn’t.

The principals are the same. This is just a basic description of simple process, this article will be updated in the future

  • Add your high level design documents
  • By the workflow – only when a high-level requirement is ready for development (for example, status=”Approved”) – send email notification to development team manager so he will add tasks, and QA team to write test cases
  • Add tasks and assign them to developers
  • Developers perform tasks and mark as finish
  • When all tasks finished for specific requirement – test cases for approved requirements can be executed
  • If bugs found – report bugs and assign to developers
  • Developer fix bugs and QA needs to verify bugs again by re-run the test cases

5 Essential Tools to Keep in touch with your Team

October 13th, 2014 Posted by Distributed development 0 thoughts on “5 Essential Tools to Keep in touch with your Team”

Author: Rami Azulay VP Marketing and Sales of Orcanos

When we just started Orcanos 10 years ago, syncing-up between 3 people turn out to be as easy as looking over my shoulder. On one of each side of me there was the CTO and Development. It was 2004 and we were a team of three. Everyone knew what are their responsibilities. To collaborate, we used our own product QPack ALM, from day one. When something required our attention you just looked up your desk. Even though “Team collaboration” didn’t require a lot of thinking or planning we found that the use of a tool did not create any overhead, we adopted new culture that become our way of standard. Fast forward to today. Our team now spread over 3 continentals. To balance this growth, we’ve continue developing our QPack ALM solution but not just for ourselves but for many of our customers. What was mostly important for us is that we will never need to leave our tool to another tool in order to perform our task. Based on this experience, here are our top five tools for team collaboration.

1. QPack Dashboard

QPack Dashboard is the main app we use to collaborate across different departments or teams. You can specify boards for each role or department and project. It helps you to keep everything on clear communication channel which created transparency between processes and team members.

In the center of your office, you can place a big screen with auto refresh report that keep displaying real time data. This keeps your team in sync and gives everyone a top down overview of what’s going on at any particular time. The other part is the proactive messages that QPack keep sending gently to any team member in order to get to speed with what the rest of the team is up to, this is all with upto date convenient (and visually appealing) way.

QPack ALM works as a board system, it can display different methodologies data such as Agile elements but as well other parts related to the lifecycle of your product such as Service Center to pick up your customer incoming service calls or your outdated documents that needs to be revised or used with the new software. It can in cooperates the 4 Blocks methodology used by enterprise: What I had to do Last Week, What Is left from last week for this week, What I need to do this week, What I need to do next week. On QPack ALM Dashboard, the possibilities are endless.

2. QPack Work Item Tracker

QPack comes with support of 36 different work items, this is what we have learned in the past 10 years that will cover almost all what you need to develop high tech product. You can use QPack work item tracking to plan and deploy software. 70% of your organization population will be using it as primary tool for development and design, testing and track bugs, technical support and customers.

QPack is something of new way of thinking that has become the trusted by Quality Assurance Developers and Testings teams at Given Imaging, Covidien, Medtronics, Luminis, Rewalk, Mazor Robotics, Matrix and experimented by GE. Quick warning, though — Once you go QPack you never Go Back, with QPack you get to use to be in control at all times and working with information spread over several system become a barrier to your day to day work. QPack is a “Simple Tool for Simple People” You can tell this was software built by people with hands on practice of over 20 years in the industry. QPack was meant to help teams ship outstanding complex high tech product and make it easier task.

However, you need to invest time into learning how to best use the software. Orcanos professional service gives you a 3-5 days workshop at your site working with your team and members One on One giving them best practices from most recent vendors they are meeting with and build your internal ALM master that will support your ongoing needs. QPack Work Item Tracker is a software that everyone can essentially live in and can rest assured the creators have their best interest at heart.

3. QPack Document Control

QPack Document Control comes to solve writing collaborations. When there is too much back-and-forth between various draft versions of the same task or feature or even just a DEFECT. With QPack Document Control, you are able to get the whole team involved in writing, while easily staying organized. What unique about QPack Document Control is the ability to work on the same document simultaneously while each member works on different area of the document. QPack allows you to break the document to the smallest pieces such as paragraphs or what is called traceable items.

QPack DMS™ is basically a super-easy, more user-friendly version of Google Documents. While Google Docs has it’s advantages, you team will be attracted to the simplicity of QPack DMS™ with the to perform chat conversation on any topic. This chat is an internal tool created by QPack which logs every conversation on the repository so team can recall ideas and solutions from the past and reuse them again for their work.

QPack DMS, allows you to create, share and collaborate visually folders, files, work items and defects. It has a clean layout that makes it looks more like a chat thread than a document. Most importantly, it offers the ability to view previous comments and versions of the document. It has strong electronic signature capabilities so members can sign off each work item within the document and freeze that work item from any further changes. It has deep copy capabilities that like in the source control can create TAG on single work item or a whole document.

You can now handle most of our document collaboration on QPack DMS™. Your team will appreciate how easy it is to get new team members started on it.

4. Online Storage for Your Business

QPack Online Storage abilities is an outstanding tool that allows you to share files in a very simple and easy way. It allows each team member to have access to important documents at any particular time.

If a your support team member is out at a meeting, and you need to share with your client some technical materials, you can open up the your QPack Mobile device and easily share files right then and there. There’s no need to fumble through emails, search and confirm the file they are using is the most up-to-date version. It will obsolete old versions of your files and keep the most updated one at first. All files are shared in centralized location there they are also updated automatically. A distribution message can be fired from QPack on each update if needed so the system proactively promotes important files to external or internal members.

Everything from access to keynote presentations, videos, press kits, logos, team photos and contracts are all conveniently stored in one central location for team member to grab it.

5. QPack Chat

Here is now the best for last. QPack Chat is truly magnificent feature, natively integrated into our QPack ALM system. It will become the core of all your team communication. We like to think of QPack Chat as the “Internal Facebook” for your team’s to communicate with each other and to collaborate on actions.

When you first start using it, you might think QPack Chat is just another internal messaging system. When you explore a little deeper, you find how well it integrates with other collaboration tools your team is currently using. The product managers at Orcanos realized it didn’t have to be the end-all-be-all of team communication apps. It just has to be an extension to all the other apps team members are using. It should be available for everyone and it should control what needs to be said internally vs. what needs to be exposed on the public domain and that can be done all in the same Chat area of the work item.

QPack Chat allows you to create chat rooms on the same topic. All chats are being recorded on the QPack repository. In case you are not connected to the chat room and still there is an update on the chat, you will receive updates on the chat to keep you in track.

QPack Chat also makes it easy to share documents and attachments. When you want to share a file, just upload it into QPack Chat, on the chat room you want it to go to and that’s it. Everything stays organized and highly searchable.

Orcanos challenge was also to make your tool selection as easy as possible. We tried to make a tool that “one-size-fit-all”. QPack ALM is the silver bullet management application. Our marketing team have learned this through direct engagement with the users and customers trying to bring on board every single department into the same app.

Our designers keep in mind that what one department/person might find intuitive, another might find complex or confusing. While your development team loves simplicity, your marketing team can not give up the office tools they are used to. And That’s ok. Each member prefers and stick to what works best for him but they all stay in the same place use the same tools and gain the same practices to do their job to the best of their ability.

When it comes to your team collaboration, your results may vary depending on your existing organizational culture at starting point. Orcanos professional team will save hours and days of trial and error to find the right combination use of features across your organization. Do not be afraid to switch and try something new If you feel things aren’t flowing as well as they should. At the end of the day, you are improving your team working environment and they will thank you for it.

 

QPack Web – making it work with distributed teams

October 9th, 2014 Posted by ALM 2.0, Collaboration, Distributed development, IEC 62304, Requirements Management, Test Management 0 thoughts on “QPack Web – making it work with distributed teams”

Recently, I get lots of queries regarding “How QPack can help us managing distributed teams?”

Well, QPack has all it takes for managing and control a distributed development project.

In this post I will describe in short what are the main QPack tools that are used for distributed development.

Later on, I will give you our best practice and some tips of how to start and how to make it work.

So,

whether you are a Project manager, product owner, project manager, software manager, tester or developer – you can use QPack collaborative tools and methodology for creating productive, distributed development teams using .

qpack_dashbaord

Web based system

For first, in order to implement a good collaborative environment, QPack web interface should be used, at least for the end users.

QPack Web is HTML5 based, and accessible using any browser and any operating system, thus making it accessible anywhere anytime.

Integrated ALM system with one repository

QPack in it’s nature is an integrated ALM system. QPack suite offers all modules required to manage a project, from market requirements definitions, to system and software requirements, detail design, test plan, test cases and test execution with defect tracking and task management, so every participant in the process has his own interface and everyone shares one central repository.

Full permissions and personalization

In QPack Web admin interface it is very easy to setup user profiles, and admin can decide with just few clicks who will see what and who can do what.

Instant messaging

A unique and integrated instant messaging allows every participant in the process to share his ideas, ask questions and provide information.

the uniqueness of QPack instant messaging is in that every discussion is saved as audit log of the specific work items history (such as customer requirements or a defect). Users can later on go back and track decisions taken. It actually replaces conversations, emails, and uncontrolled documents

Queries, Alerts and notifications

by defining queries and alerts its very easy to track information and get notifications in “Push” mode, where QPack sends alerts containing activities to perform based on predefined rules.

Dashboards

Whether you are a developer, tester, or manager, you can personalize your dashboard accordingly.

You can setup any type of report

 

Orcanos

Contact

8 Tozeret Ha'aretz Street
Tel Aviv, Israel
+972-3-5372561
info@orcanos.com

Copyright © Orcanos, All rights reserved. | Privacy policy | Terms of use