Created
August 26, 2019 15:27
-
-
Save Patru/505681f2d52431d78c48018688be1b9f to your computer and use it in GitHub Desktop.
How not to find a Software Engineer for an agile team
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
I ran into this job description: | |
Tasks | |
As a member of a delivery team: | |
• Collaborate with Product Owner to create and refine User Stories and Acceptance Criteria, as well as confirm that the code and acceptance tests reflect the desired functionality | |
• Participate in Product Increment and Iteration Plannings by: | |
• Analyzing the product and team backlog items | |
• Estimating the work effort | |
• Committing to the iterations and Product Increment objectives | |
• Creating Iteration Plans and Iteration Plan objectives | |
• Perform SW-engineering tasks in adherence with the established procedures and guidelines | |
This includes: | |
• Conduct research, design, prototyping and other exploration activities to meet functional requirements and quality attributes | |
• Implementation of the design into code maintaining the quality standards and metrics agreed at team level and promote best SW quality practices and processes in the team | |
• Implementation and performance of SW-tests on unit and integration level and write automated acceptance tests | |
• Provisioning documentation on all levels (code, unit, test, …) | |
Support the system tests and global support organization by: | |
• Analyzing incidents, problems and defects | |
• Fixing Software-Defects | |
• Provisioning of patches and releases | |
• Participate in the iteration evaluation | |
• Support the presentation of the iteration deliverables | |
• Support continuous improvement by providing feedback in the iteration | |
• Do retrospectives and discuss on the processes | |
• Be transparent providing work status and issue notification to the organization, including line management | |
• Support when required the projects and product maintenance in the full range of the Software-Development process as it is defined in SIS, including CI/CD environments | |
As a member of the capability organization: | |
• Actively contribute to the continuous improvement of the Software Engineering Discipline at DIA Common Assets | |
• Contribute in spreading and increasing the knowledge, skills and capabilities with the rest of members as well as leading initiatives/activities related to the Capability purpose on your own | |
Skills | |
• University degree in software engineering or equivalent work experience | |
• Experience working in agile development teams | |
• Experience developing and mastering development environments (configuration tools, automation, simulation) | |
• Teamplayer | |
• High quality awareness | |
• Customer orientation | |
• Experience in modern C++ | |
• OOA/OOD with UML | |
• GNU/Linux, shells, git, python, make | |
• Covering realtime is a plus | |
• Languages: German and English |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Now I think this is a "brilliant" example of an agile transition gone brutally wrong. Not sure how to fix this though.
(P.S.: Of course I did not apply ...)