Friday 14 September 2018

Thought of the day: Questions to ask your clients and developers?

There are times when it is a great idea to ask your clients and your developers a few questions about the project you are about to join.

Naturally, you will not be able to ask all the people the questions but you never know.
However, the answers should give you a rough idea of the maturity of the project.

The following table is an overview of the detail & questions you may need from each of the stakeholders. You may determine that additional/different people are needed to fulfil this and some people may have multiple roles but it should be a starting point.


Who (Client)
Information sought
Project Sponsor
  1. Provide an overview of the Objectives and benefits expected
  2. What are the Business’ general expectations of the project? How are they being assessed?
  3. What are the Business’ technical expectations of the project? How are they being assessed?
  4. What are the Business’ security expectations of the project? How are they being assessed?
  5. Is there a feature project roadmap and is it shared with the Team?
Product Owner

  1. Provide an overview of the prioritised delivery roadmap
  2. What are the Business’ general expectations of the project?
  3. What are the Business’ technical expectations of the project?
  4. What are the Business’ security expectations of the project?
  5. Is there a feature project roadmap and is it shared with the Team?
  6. What security requirements has the business placed on the system?
  7. What non-functional and performance requirements has the business placed on the system?
  8. What is the current and future growth of the system expected to be?
  9. Are requirements prioritised using a MoSCoW scheme?
  10. As PO are you involved in the Sprint planning phases of the project?
  11. Are you involved in the development of the project feature backlog?
  12. Are you involved in the development of the sprint planning process?
  13. Are technical blockers reported to you?
  14. Is there sufficient project information being provided by the team to assist with the creation of further requirements?
  15. Provide a walkthrough of the feature backlog and priority
  16. Provide insight into the current issue/risks/constraints to the project
Project Manager
  1. Provide an overview of the current SDLC, measures and controls
  2. What are the processes & tools for requirements control?
  3. Does the project have a Release timeline?
  4. What is the process the team is following to control their development? If it is agile can you describe the process?
  5. Who is involved in the development of the project feature backlog and whats the process?
  6. Who is involved in the development of the sprint planning process and whats the process?
  7. As PM how would you describe your role in this SDLC?
  8. Does the project have a measurable sprint velocity?
  9. As PM are you involved in the Sprint planning phases of the project?
  10. How are testing outcomes & blockers/impediments reported and tracked?
  11. Are technical blockers reported to you?
Data/Business Analyst
Business SME
  1. What is the Business’ general expectations of the project?
  2. Provide an overview of the top priority Use Cases for the solution
  3. What are the processes the system needs to perform?
  4. What is the current quantity of data the system must process?
  5. What are the data sources, transformations and outputs the system must perform? (schemas, definitions, data flows etc)
  6. What security requirements has the business placed on the system?
  7. What performance requirements has the business placed on the system?
  8. What is the current and future growth of the system expected to be?
  9. How are the requirements communicated to the team?
  10. How is system functionality measured against the requirements?
Technical Architect
  1. What is the overall System architecture context?
  2. What are the main functional components of the system?
  3. What are the processes & tools for requirements control?
  4. Are you involved in the development of the project feature backlog?
  5. Are you involved in the development of the sprint planning process?
  6. What security requirements were placed on the system?
  7. What performance requirements were placed on the system?
  8. What is the current and future growth of the system expected to be?
  9. What architecture requirements were placed on the system?
  10. What other non-functional requirements were placed on the system?
  11. Is there a Disasters recovery plan for the system? If so how is it implemented architecturally?
  12. Is it possible to get access to all existing design notes for the system?
  13. How are design choices and patterns communicated with the team for development?
  14. Is there a deployment strategy or process for the system? (Infrastructure as code?)
  15. Is there a testing/assurance strategy or process for the system?
  16. When there are issues with the development are you informed and consulted?
  17. When there are issues reported by assurance are you informed and consulted?
  18. Prior to the system going operational are you consulted by the Assurance, Operations or development team on how systems should be configured, or any potential issues?
  19. When in operation do you have visibility of operational monitoring systems?
  20. Once the system is deployed how do you know that it has been deployed according to your specification?
  21. Does the system have a ‘Technical Debt log’ or a list of known issues?
  22. Provide an overview of the solution architecture
  23. Provide details of constraints, dependencies and issues encountered and impacting delivery
Vendor Tech Lead
  1. How are requirements communicated to the team?
  2. What is the process the team is following to control their development? If it is agile can you describe the process?
  3. Are you involved in the development of the sprint planning process?
  4. Is the team aware of the release schedule for the system?
  5. Is the team recording development information in some way? If so using which tool?
  6. What security requirements were placed on the system?
  7. What performance requirements were placed on the system?
  8. What architecture requirements were placed on the system?
  9. What is the process of reporting progress in development back to project management?
  10. What are the development toolsets in use across the team?
  11. When source code is developed what coding standards are being followed?
  12. When source code is being developed which source code management (SCM) tool is in use?
  13. Who has Source code access?
  14. When a build of the system is performed what are the build artefacts and how are they stored?
  15. What is your SCM versioning & branching & merging strategy?
  16. When defects are found, how are they reported, tracked and reported?
  17. What are the capabilities of development staff & their relative strengths?
  18. Is the team following a BDD/TDD development approach?
  19. What level of code review is performed during development?
  20. What is the release process for new functionality?
  21. Do you produce release notes for each new release?
  22. How many environments are used for development?
  23. What is the process for procuring cloud development stacks?
  24. What are the data sets used during development?
  25. How is the development environment secured?
  26. Is there a build process for the system? If so what is it?
  27. Is the system deployable using automation tools? If so what are they?
  28. What level of testing (manual & automated) exists for the system to prove functional & non-functional requirements?
  29. When the system is in UAT what information/documentation is requested by Assurance to determine the available functionality?
  30. When the system is in LIVE what information/documentation is requested by Operations regarding its operation and deployment?
  31. Provide an overview of the solution and the code
  32. Provide details of constraints, dependencies and issues encountered and impacting delivery
  1. Security & Compliance

  1. Provide an overview of the prioritised Security & Compliance requirements for the solution
  2. When the system requirements are being determined was security consulted?
  3. When the system is being developed what involvement does Security have?
  4. When the system deployment is being planned is Security consulted?
  5. Is Security informed of code related security issues?
  6. Is security informed of how the system is tested for compliance with security requirements?
  7. When operational how is the security of the system managed?
  8. If there is a security issue with the system how are you informed?
  9. What is your process for reporting a security breach?
  10. Provide an overview of constraints & dependencies for delivery
Assurance Lead
  1. Provide an overview of the testing strategy and framework
  2. Provide an overview of the test coverage on the solution and the measures in place
  3. What involvement does assurance have in the code-Review process?
  4. What level of functional testing does assurance perform on the system?
  5. What level of non-functional testing does assurance perform on the system?
  6. What proportion of the testing is automated vs manual?
  7. Does the system have automated test reports and how are they reported to assurance
  8. What is the test plan for penetration testing?
  9. How does assurance get involved with the defect management process?
  10. Does assurance have any input on the architecture of the system?
  11. Once deployed what involvement does Assurance have with the system?
Operations
  1. Provide an overview of the path to live/transition to live process.
  2. When the system is being designed what visibility do you have or need of its functional requirements?
  3. When the system is being designed what visibility do you have or need of any security requirements?
  4. When infrastructure is needed by the Development, Test and support team what is the process they must follow?
  5. How are you informed by development of the build artefacts needed for deployment?
  6. How do you enable or control the provisioning of cloud resources by the development team?
  7. What information do you need regarding the security of the proposed system?
  8. What information do you need about the testing process?
  9. How are deployment details of the Deployment & Configuration process communicated to you?
  10. What is the process for post-deployment system testing?
  11. How is performance and systems failure reported?
  12. What are the Monitoring processes and how & what is reported?
  13. If the system has a bug how is it reported and who does the repair work?
  14. What are the system’s supported hours?
  15. What is the systems supported availability?
  16. What is the DR plan for the system?
  17. When in operation does development have access to the system to perform fault analysis?

 Have fun!