Pyxis Training's new website becomes Pyxis Doceo!


Agile Architecture, Analysis and Modeling

Today, companies that develop software products are invited to be more reactive and effective. Agile approaches seem well suited to this new context by offering solutions with high-added value for users.

For example, the Scrum method explains how it is possible to plan development considering business value in collaboration with experts in the field. However, the Scrum method, which is not very normative, needs to explain how software development disciplines must be adapted to an incremental and iterative approach, contenting itself with talking about emerging architecture, analysis and modelling.

Agile methods may seem light and improvised for organizations that have implemented rigorous processes. In particular, they need to consider the importance of analysis work upstream to manage the technical risks associated with software development projects.

Content :

  • What is software architecture, and what are its different variations?
    • The challenges of risk mitigation and complexity management
    • The role of architects and analysts
  • What are agile approaches?
    • Overview of the Scrum method
    • Advantages and repercussions of agile approaches on the roles of the architect and the analyst as well as on the discipline of analysis
    • Distinction between the cascade method and agile methods
  • Principles of emerging analysis
    • Balance between anticipation and adaptation during the work arising from the elicitation
  • Systemic vision
    • Determination of what is sufficient to launch development work
    • Workshop: Analysis practices and high-level deliverable goods, such as the Vision Board, the Project Charter, the Product Canvas, the Story Mapping
  • Management of the required elements
    • Product book tool and collaboration with the Product Owner
    • Planning according to business criteria and technical considerations
  • Drafting of the required elements
    • Empirically writing requires elements of quality
    • User scenarios tool (User Stories)
    • Technique of cutting scenarios, kano, spikes, invest, the definition of “finished” of scrum and sashimi
  • Project monitoring
    • Use of scrum inspection points to achieve product objectives
    • acceptance of increments during the iteration review
    • Improvement of practices during retrospective
    • Quality and technical debt management with the product book
  • Agile documentation
    • Document of documents empirically
    • Reduction of the writing effort and the waste of documentation
    • Documentation according to the life cycle and the usefulness of deliverable goods
  • Role of the agile architect
    • How to exercise leadership in an agile context
    • Delegation according to the subject and the context
  • Role of the agile analyst
    • How to contribute as an analyst within an agile team
    • Collaboration with the development team and the product owner
    • Behavior and responsibilities

This training is:

Online Languages


3 hours in three 5 -hour workshops

Classroom pricing:

$995 CAD + tx

Public Sessions

Private Group

Have a group of 5 or more students? Request special pricing for private group training today.

Private Group Training


  • Learn to balance upstream elicitation and an emerging approach.
  • Learn to mitigate technical risks with agile approaches.
  • Learn how autonomous and multidisciplinary teams use the required architectural elements.
  • Understanding the design of solutions, 'Analysis and documentation in an iterative and incremental way.
  • Know the impact of agile approaches on the role of the architect and the analyst.

Target Audience

  • Architecture managers
  • Analysts
  • Technical leaders


At Pyxis Doceo, excellence guides every training program. Our programs follow high quality standards and are updated annually. Each session is enriched by interactive workshops and exercises, fostering connection between participants. You don’t just learn, you transform.


What are the main problems addressed by this training?

For organizations with rigorous processes in place, Agile methods can seem lightweight and improvised. In particular, they need to consider the importance of upstream analysis work to manage the technical risks associated with software development projects.

What's in it for me?

We are mitigating technical risks with Agile approaches.

Is this training for me?

If you want to learn how to apply the Agile principles of iteration, modelling and documentation to my company's rigorous architecture and analysis processes, this course is for you.

Private Group Training

Contact us to arrange private group training for this course.

"*" indicates required fields


Related Articles You Might Be Interested In