You need to manage engineering workflows. Which tools are the most effective?

From my experience, I find Atlassian's Jira is the most effective for true Agile design of software. It also has a host of dashboards for daily and weekly check-ins, management reviews etc.

I love Wrike for project & task management as well as progress analysis. Jira is good for agile projects, but usually needs too much customization to generate progress clarity. Confluence is nice for document management and co-authoring.

1. Project Management: Jira, Asana, Trello 2. Collaboration: Slack, Microsoft Teams 3. Version Control: Git, GitHub, GitLab 4. Continuous Integration: Jenkins, Travis CI 5. Documentation: Confluence, Notion

Efficient management of engineering workflows is crucial for successful project execution. For industrial projects, we generally use an Engineering Document Management System (EDMS) that facilitates efficient document management, version control, and collaboration throughout the project development and execution lifecycles. The key features of an EDMS are Version Control, Access Control, Workflow Management, Integration with other third-party applications, Change Management, Search and Retrieval of documents, Audit for compliance and accountability, and Collaboration by allowing multiple users to work on documents simultaneously.

Effectively managing engineering workflows involves a variety of tasks including project management, version control, continuous integration/continuous deployment (CI/CD), and communication among teams. Here are some of the most effective tools for each category: Jira,Git,GitLab CI/CD,SonarQube,Confluence,Slack,Grafana,Zapier

When we started using GitHub Discussions for feedback and ideas for planning and knowledge-sharing, it helped a lot to store info in one place and not to be overwhelmed by keeping up-to-date different tools. As a software engineering manager, you can use it with your team to help your engineers expand their experience in using GitHub. It is especially good for distributed remote teams as it helps with asynchronous communication.

Collaboration tools are designed to enhance teamwork and communication among project stakeholders. They often include features for document sharing, real-time editing, communication channels, and task assignments. Effective collaboration tools can lead to improved productivity and a cohesive project environment. Slack and Microsoft Teams are popular options that integrate with various project management and documentation software.

Communication is key! - So many types of real-time communication apps out there, consider those that are secure and of course reliable. - Maintain comms with your team and encourage the same from everyone, remember that seemingly small contributions add up to the major good of any project.

In my experience, Jira has proven to be effective as a tracking tool. it's easy to use and has countless ways to visualize your progress through dashboards. With the right reports and graphs, you can easily identify bottlenecks.

Embarking on a challenging software project, tracking tools emerged as our unsung heroes. Project management software orchestrated seamless task assignments and progress monitoring, akin to an ever-vigilant assistant. Issue tracking systems acted as guardians against bugs, documenting and overseeing resolutions. Code analysis tools served as secret weapons, ensuring the robustness of our codebase. Dashboards became visual storytellers, conveying our journey in real-time to stakeholders. In the complex world of engineering workflows, these tools weren't mere instruments but transformative allies, turning challenges into triumphs and projects into legends.

Tracking tools provide visibility into the progress of projects and the performance of teams. They can track time, costs, resources, and quality metrics against the project plan. This real-time data is vital for making informed decisions and adjustments. Jira and Trello are examples of tracking tools that offer customizable dashboards and reporting capabilities.

In engineering workflows, testing tools ensure that the product or system meets specified requirements and standards. These tools can range from software that conducts automated code tests to hardware that measures the performance of physical systems. Quality assurance relies heavily on these tools to validate the integrity and safety of engineering outputs.

From my experience, use GitHub and GH Actions if you are a small team. For the enterprise level, I can recommend TeamCity from JetBrains as a more configurable and flexible tool with fine-grained access control. Other good options are Jenkins as an alternative for TeamCity and GitLab CI/CD as an alternative for GH Actions.

Deployment tools assist in the delivery of engineering projects from development to production. In software engineering, these might include continuous integration and continuous deployment (CI/CD) tools like Jenkins or GitLab CI. In hardware engineering, deployment might involve tools for managing the logistics of manufacturing and distribution.

When managing engineering workflows, selecting the right tools can greatly enhance productivity and collaboration. From organizing tasks to facilitating communication and version control, there are several effective options available. Whether it's streamlining Agile project management with Jira or simplifying task organization with Trello, finding the perfect fit can significantly boost your team's efficiency and success.

Go beyond Engineering when searching for planning, management, or collaboration tools. Look for ecosystems like Atlassian or others that allow information to relate or synchronize across all levels and departments of business so you don't end up with walled gardens. You don't want to have to update a notion database, a powerpoint slide, a spreadsheet, and send a slack message every time a Jira ticket is completed.

usually include project management software for task tracking, Also use Microsoft Teams for communication, collaboration, version control systems, etc, and specialized engineering tools for continuous integration and deployment. It ultimately depends on your team's specific needs and preferences.

It's not the tool that is important; it is the business process that needs to be solid and then correctly modeled in the tool of your choice. There are of course considerations in tool selection like cost, support, and some tools are fundamentally written to support specific domains such as ES&H, where an OOB solution may require only moderate customization.

Classic Jira has a very nice customizable workflow system that would suit the needs of almost every team and project. If you need more integration with pipelines, commits etc., try Azure DevOps.