Project Management Software for the Software Industry

Live the Scrum process: Projektron BCS as Scrum software

Do you also rely on agile software development according to Scrum? The framework impresses with its simple structure and predefined roles, can be implemented quickly and ensures flexibility and transparency. Projektron BCS is open to methods and also supports your development projects according to Scrum, while remaining highly customizable and able to adapt to your specific Scrum approach.

	Scrum Roles: You map the usual Scrum roles such as Scrum Master or Product Owner in BCS via user licenses and roles. This gives each team member the necessary access rights.
	Daily Scrum: BCS supports you with a task overview in which processing status the requirements and activities from your Sprint Backlog are currently located. Each team member can select an activity for processing or mark it as implemented with one click. This serves as a reliable basis for the daily planning of your Scrum team.
	Burndown chart: A burndown chart with cumulative flow diagram can be integrated into the task overview, which graphically displays the sprint progress. Projektron BCS visualizes the processing status of the requirements in color and displays the ideal chronological sprint progression as a reference.
	Scrum Board: Depending on the column into which you move your activities from the user stories via drag & drop, the status of the respective activity changes automatically. Colored markings make it clear which activity belongs to which user story. Via drag & drop you assign team members to the activities. As in Kanban, you can set a work-in-progress limit.
	Product Backlog: Structure and refine the requirements for your product with epics, user stories, subrequirements, activities and acceptance tests. Directly in the Product Backlog, you can also create the required Scrum structure elements, move them via drag & drop and prioritize them. Team members and product owners can communicate with each other directly on user stories and epics. You can also see the communication process and the most important changes directly on the Scrum element.
	Sprint Planning: In the planning view of the product backlog, Projektron BCS shows you the sprints of your Scrum project that are still open. Possible sprint assignments and processing sequences of the user stories can be run through using drag & drop. Projektron BCS takes into account the development speed of your team (velocity) as well as the estimated story points of your user stories and informs you about capacity.
	Sprint calendar: Whether sprint planning, daily scrum, sprint demo (review) or sprint retrospective: In the sprint calendar, you automatically generate regular meetings of your scrum team.
	Scrum with multiple teams: If you are working on a large Scrum project with multiple development teams, the planning view in the Product Backlog allows you to organize your user stories clearly, even in multiple sprints running in parallel.
	Resource planning included: BCS allows you to reserve staff capacity for individual sprints or for the entire Scrum project. You can quickly check how much free capacity is currently available in the resource preview.
	Time recording included: Your Scrum team posts the effort incurred directly to the processed user stories, subrequirements, activities and acceptance tests. Projektron BCS adds up the booked times along the product backlog structure. As a product owner, you know exactly how much time and effort it took to implement a user story or a product increment, for example, and can make a target/actual comparison. Using Projektron BCS invoicing, you can invoice your customers for the booked efforts on a project-specific basis.

Agile, classic, hybrid - open-method project management

In addition to Scrum, BCS offers you all the functions you need to run project management according to other methods, for example:

V-Model® XT

V-Scrum

Automotive SPICE

Kanban

According to IPMA/GPM

Nach PMI

PRINCE2

Hermes

Development in Jira - Project Management in BCS 

Using the bidirectional interface to JIRA Server and the unidirectional interface to JIRA Cloud, you can easily and flexibly integrate JIRA tasks (issues) and JIRA work logs into your Projektron BCS project. With the interface you: 

	transfer tasks, work logs or estimates from JIRA to BCS.
	flexibly exclude individual user stories, epics, etc. from synchronization as an option.
	easily embed JIRA tasks in your Projektron BCS project and thus include development efforts in your controlling evaluations.
	identify potential bottlenecks while your team is already working on JIRA tasks in the resource preview and use free capacities efficiently.
	keep track of the progress of your entire project with Gantt charts, target/actual comparisons and traffic light functions.
	identify undesirable developments early on by forecasting time and budget overruns and take timely countermeasures.
	generate project reports easily and inform stakeholders quickly and as needed.
	invoice projects including the efforts from the JIRA work logs conveniently.

Projektron BCS provides holistic support for your project work: From the sales process to quotation creation, project planning and control including resource planning and invoicing, the system covers all areas that are necessary for successful and efficient project implementation.

With precise scheduling and informative resource forecasts, development projects, support projects and maintenance projects can be handled efficiently and cost-effectively. During the course of the project, the precise project controlling and timely project reporting enable you to provide your customers with information at any time. The detailed analysis options offer you ideal conditions for continuously optimizing your individual workflows and internal processes.

Do your development teams work at different beach locations? With the web-based project management software Projektron BCS, you can bring the team together thanks to integrated calendars, appointments, meeting planning tools and central access to projects and documents.

Your employees can easily access Projektron BCS via web bowser from their workstation in the office, in the home office or on an external appointment with customers or partners. However, not only your team members, but also your customers and external project staff are actively involved thanks to browser-based access, a suitable license structure and detailed rights management. Project participants with the appropriate rights access the same central database regardless of their location and have an overview of tasks, deadlines and schedules.

By integrating your customers, you create transparency. Your customers are informed not only about the current status of the project work, but also about resources, efforts and costs. You shorten approval processes to a minimum through direct communication via BCS. Trustful cooperation, time and cost savings have a positive effect on all parties involved.

Ticket system in Projektron BCS - Versatile for internal organization and external communication

The ticket system in Projektron BCS opens up several options for you:

	Customer communication in the form of your own support portal
	Internal task allocation and work organization within the scope of project tasks and line activities (Kanban board)
	Flexible task- and project-related effort recording for precise billing
	Exchange and documentation within the scope of cooperation (also across locations)

Your support portal with the ticket system from BCS

Do you process incoming customer inquiries and complaints via e-mail? Or would you like to offer round-the-clock customer service, but are struggling to keep your hotline continuously staffed? Does your support team find it difficult to prioritize customer queries and assign them to the appropriate agents? The ticket system in Projektron BCS is the ideal solution to make your support customer-centric, productive and efficient.

A ticket system forms the direct interface between your customers and your support team. Customers can enter requests and error tickets, support staff use the tickets for organization, documentation and billing. A ticket system in support therefore offers a variety of advantages for you and for your customers:

	Centralization: a ticket system records incoming requests and stores the contact history centrally in one place, cross-channel and context-related. This means that all relevant information, from the contact history to the digital customer file to the current processing status, is clearly available to every agent via the software.
	Automation: The ticket system considerably simplifies routine tasks and the organization of inquiries once appropriate workflows have been defined. These include the recording of requests, transfer to a digitally standardized format, categorization, prioritization and initial evaluation.
	Time savings: Capturing user requests in tickets saves first-level support work in recording and classifying a request. The customer, as the ticket creator, already makes the necessary entries independently, without a support employee having to query information or request supplementary material from the customer.
	On-time processing: The ticket system makes it much easier to comply with your SLA (Service Level Agreement) guidelines. Reminder functions and prioritization levels ensure that your service agents process customer inquiries and error tickets on time. If an employee fails to meet deadlines due to overload or absence, escalation rules ensure that the ticket is taken over by other agents.
	Evaluability: Tickets are stored with all information and processing histories and can be evaluated. This makes it easy to evaluate and optimize response times, ticket volumes and average communication efforts. You can see unnecessary work steps and too much effort, keep an eye on your team's performance and easily adjust workflows.
	Transparency: The customer can track agents, processing status and progress in detail. This helps them to build trust in your company and to understand calculated efforts more easily.
	Availability: Even if your customer support or help desk cannot be manned around the clock, the ticket system remains available to customers 24/7. The ticket system informs the customer about every status change.

Thanks to precise separation between external and internal data, the external support portal ensures even greater security and particularly high data protection. Transferred information Data is transferred in both directions between the external support portal and the internal Projektron BCS - but not all of it. For example, only data that your customers are allowed to see ends up on the external support portal, while you see all the information you need to process a ticket in the internal Projektron BCS.

The exchange of files is also possible: The associated file storage of the support portal is also displayed on tickets in the internal Projektron BCS. In this way, you see both external and internal files in one view and can move or copy the files if necessary.

Tickets for Scrum

If you work with the ticket system from Projektron BCS, you can easily transfer internal inquiries and customer requests for your products into your Scrum projects.

For example, if a customer requests a new function via ticket, you can create the associated user story in the Scrum software with just a few clicks and add it to a product backlog. The ticket description can be easily adopted for user stories and activities. Projektron BCS links the new user story to the original ticket, making it easy to trace the background of its creation, for example when prioritizing the product backlog.

In addition, tickets can be linked to existing user stories, epics or partial requirements.

Data security guaranteed throughout the entire software lifecycle

Who hasn't experienced the situation where the customer's data protection officer throws a spanner in the works shortly before the release? By taking a preventive approach, you can strategically establish tightly described guidelines and high standards in the area of data protection. We apply these standards to the development of Projektron BCS and enable you to develop secure software with BCS.

By implementing the following measures, among others, we ensure a high level of data security and significantly reduce the risk of data breaches and other security incidents:

	The BCS internal password vault ensures that all passwords used in the software development process are stored in a secure, encrypted location. This increases security, as passwords are no longer entered in configuration files and passwords cannot be read from the password vault by unauthorized persons.
	Certificate management ensures that all digital certificates used in the software development process are valid and secure, and that they are used correctly and consistently.
	Our development and hosting team is ISO 27001 certified. We have implemented comprehensive security controls in line with the standard to protect sensitive data.
	Two-factor authentication adds an extra layer of security to the login process by requiring users to provide two forms of identification. After entering a username and password, BCS also requires users to scan a QR code or enter an authentication code using the TOTP method. Each user can enable 2-factor authentication for themselves in their user account
	Ongoing penetration tests help us to identify and eliminate vulnerabilities in the Projektron BCS software development process by simulating the actions of an attacker.

Data protection-compliant software development

According to the General Data Protection Regulation, software manufacturers must comply with certain requirements when developing software solutions. BCS supports you in meeting these requirements of the GDPR for the processing and storage of personal data, for example thanks to:

	Anonymization function for test installations: By implementing an anonymization feature, users of a BCS test instance can ensure that sensitive data is not exposed and reduce the risk of data breaches. In addition, test data can be shared with other teams or third parties without compromising data privacy.
	Presentation anonymization feature: Ensure that sensitive data is not exposed during presentations. This can be especially useful when data is shared with external parties or presented in a public environment.
	Customized deletion procedure for old data: Define individually what type of data, when and how securely it should be deleted. This ensures that you comply with legal requirements and protect your customers' privacy.