Bryan Bryant Email & Phone Number

Bryan Bryant is a Staff Accountant at NoiseAcct Services LLC. They possess expertise in systems design, agile testing, software design, requirements analysis, requirements management and 35 more skills. They is proficient in Japanese. Colleagues describe them as "Bryan and I worked together on a program, I as the Program Manager. Bryan has a unique gift of being able to take strategic goals/needs and break them into executable pieces. He took a team of 40 software and algorithmic developers and brought process and standardization to that team. That team was responsible for developing and maintaining over 4 million lines of code in multiple languages. Bryan also brought a defense program into Agile Software Methodology. Bryan's organization, technical interpretation for management, metrics, knowledge of software architecture, process, standards, agile, and project management allowed this very traditional defense program to move into the agile world. The end result was a more satisfied software team, an enlightened program management team and end user satisfaction. I would highly recommend Bryan's expertise to any program/company looking to grow its presence, improve processes or put in place an agile Methodology. While I may have worked with Bryan specifically in the software arena, his knowledge of programmatic, administrative and human resources (mentoring, training, hiring, feedback) make him an invaluable asset." and "Bryan was able to greatly impact the software development teams when he: 1) brought more effective and efficient software processes forward at the Rapid Integration Structured Improvement Activity (SIA); and 2) was named the SW Lead for the SW release which provided the catalyst to ensure his ability to shape the vision could be implemented effectively. Bryan's inputs that he championed for the SIA lead to the following results: reduction of compile time from 5 to 2 hrs, and automation of system quiescence, to reduce shutdown and startup processes. Bryan's leadership as the SW Lead resulted in the development teams meeting their commitments and the production of a quality product. FAT went very smoothly with only 5 defects written. Bryan has been able to positively influence efficiency and productivity for the SW team from FFB - forward as the SW Lead. Commitment are met for each milestone. His concerns are brought forward early and voiced at milestone meetings. Bryan clearly articulates his perspective on the reported data; he does not state things in a vague or confusing manner. He is honest in his perspective, even if leadership may not like what the data is showing. His insight into development costs for proposals is sought after by other managers. It is very refreshing to have a frank and open discussion about Quality concerns, and get a direct, honest answer from Bryan. It is clear that he has a tremendous amount of expertise in development, metrics, and capture. Bryan lead Tiger Teams in analysis of root cause(s) and identification of solutions or viable work arounds as demanded by program needs: Bryan has facilitated 3+ tiger teams 1Q and 2Q to analyze stability issues impacting development progress. I assisted Bryan with 2 of the tiger team RCAs; Bryan was able to focus the team using fishbone diagrams to identify solutions to these issues that were very critical in the program's ability to complete the internal milestones. As a result, there have been no further issues in these areas of the deliverable. Both SW Release Stress testing and FAT were very successful. Bryan provides software technical metrics to the Release Managers (defect density, ilog trending, and ilogs opened) at the beginning of the technical review week; responding to questions prior to the status meeting when requested. Bryan also provides feedback to the Technical Leadership during the bi-weekly review meetings. Bryan specifically provides me with the software sizing metrics for review and feedback prior to submittal for the customer BMR."

Listed skills include Systems Design, Agile Testing, Software Design, Requirements Analysis, and 36 others.

• 

  University Of Oklahoma

  Computer Science