Agile Manifesto Explained

Episodul 25 explică pe scurt modul în care poate fi realizată o planificare strategică a unei organizații folosind analiza TOWS. Acest tip de analiză se bazează pe analiza SWOT (presupune, la rândul său, identificarea punctelor tari și slabe precum și a oportunităților și amenințărilor ce vizează o organizație) dar ne conduce într-un mod mai direct la identificarea direcției strategice ce trebuie abordată.

The Cynefin framework was developed by David J. Snowden in 1999. It aims to help leaders understand that every situation is different and requires a unique approach to decision-making.The framework outlines five situational domains that are defined by cause-and-effect relationships. They are Obvious, Complicated, Complex, Chaotic, Disorder.Each of these domains has a specific decision-making approach that helps you make better sense of the situation, and choose the most appropriate way forward.This episode of Software Project Management podcast covers the description of Complex and Chaotic problem domains.

The Cynefin framework was developed by David J. Snowden in 1999. It aims to help leaders understand that every situation is different and requires a unique approach to decision making.The framework outlines five situational domains that are defined by cause-and-effect relationships. They are: Obvious, Complicated, Complex, Chaotic, Disorder.Each of these domains has a specific decision-making approach that helps you make better sense of the situation, and choose the most appropriate way forward.This episode of Software Project Management podcast covers the description of Obvious and Complicated problem domains.

The Agile Manifesto is a document that identifies four key values and 12 principles that its authors believe software developers should use to guide their work. Formally called the Manifesto for Agile Software Development, it was produced by 17 software development consultants during an outing in February 2001, at Snowbird ski resort in Utah.Youtube: Software Project Management | S2E02 | Agile Manifesto Explained

A wise approach when we want to adopt a new methodology, technology or simply a new practice in a project team, is to identify and compare in advance the advantages and disadvantages of its use. Every time such analysis shall be carried out taking into account the context in which it will be adopted. "Which are the benefits of implementing the practice X in my team?", "What are the main risks for my project in the conditions of implementing the methodology Y?", "Which is the learning curve of the technology Z and how will it impact the deadlines?" - these are just a few examples of questions we ask ourselves (together with our team) prior to making a decision. The unexpected trap of this process is that we usually try to fully benefit from the advantages of the methodology/technology/practice we implement and most of the time we exaggerate in this respect. The Yerkes-Dodson law (known also as "Inversed U Curve theory") gives an interesting perspective in approaching all these practices.Youtube: Software Project Management | S2E01 | Inverted U Curve and Agile Development

Episodul 24 descrie utilitatea diagramelor Gantt în construirea unui plan de execuție în proiecte predictive.Youtube: Gestionarea Proiectelor Software | S1E24 | Diagrama Gantt

Episodul 23 descrie matricea responsabilităților, cunoscută și ca Matricea RACI (Responsible/Accountable, Consulted, Informed), ce pune în corespondență task-urile identificate în WBS cu rolurile membrilor echipei de proiect.Youtube: Gestionarea Proiectelor Software | S1E23 | Matricea Responsabilităților

In episodul 22 este descrisa o structura arborescenta utilizată în determinarea top-down a activităților unui proiect, instrument care este cunoscut sub denumirea de structură defalcată a lucrărilor (sau mai degrabă este cunoscută versiunea în limba engleză Work Breakdown Structure cu prescurtarea sa, WBS).Youtube: Gestionarea Proiectelor Software | S1E22 | Work Breakdown Structure (WBS)

Documentul de inițiere a proiectului este primul document redactat de un manager de proiect. Structura acestuia poate sa difere de la o companie la alta, însă anumite informații sunt comune în toate cazurile. Youtube: Gestionarea Proiectelor Software | S1E21 | Documentul de Inițiere a Proiectului (Project Charter)

In episodul 20 este descris un exemplu in care e utilizata o tehnica de luare a deciziilor si anume analiza atributelor.Youtube: Gestionarea Proiectelor Software | S1E20 | Analiza Atributelor