Reading: Primer to Agile Contracts

Link here

Comments

Post a Comment

Popular posts from this blog

XP: Card, Conversation, Confirmation - The three C's

Image
  This is a technique lifted from XP (Extreme Programming).  Card On each card is enough text that identifies a requirement. Notes of priority and cost are written on it as well. They serve as tokens for requirements and are handed to developers during implementation and returned to customers when completed. Conversation  Conversations are collectively exchanges of thought between customers and programmers. It is largely verbal, but may be communicated with supplemental examples. Confirmation Confirmation, in other words, acceptance tests, are defined at the start with the customer and shown to customer at the end of the iteration to confirm the story's completion. Note that extra documentation, while seemingly helpful, hardly "confirms" anything and cannot replace acceptance tests. 
Read more

Notes: PM Breakdown PMBOK

Image
 Notes from  here There are five phases of project management. 1. Project Initiation  Here, you are turning an scribble into a meaningful SMART goal. Business case is defined broadly and the project charter is created. Included within the cater is the goal, scope, key stakeholders, and register of roles. Technical aspects are not yet considered yet at this stage. 2. Project Planning  The project road map is planned out. Unless it is agile, this phase is very comprehensive and may account for up to 50% of the project's time. It includes identifying technical needs, developing a detailed project schedule, creating a communication plan, and setting up goals/milestones/deliverables.  3. Project Execution  Deliverables are being met.  4. Project Monitoring and Controlling Simultaneous with Step 3, PM makes sure that project objectives are being met and everything is good smoothly between the team and stakeholders. PM ensures that there is minimal deviation ...
Read more

Concepts of Skill Acquisition for Scrum Master

Image
Below are some frameworks for Scrum Masters to help understand how their scrum teams may learn and develop competency. It serves as a reference and does not, in particular, dictate anything.  Shu-Ha-Ri  This is the Japanese model of skill acquisition, which Alistair Cockburn has personally referenced. It comes from Aikido, and it outlines that students goes through three stages: Shu, Ha, and Ri.  Shu - student follows masters teachings without question, understanding, or desire to make judgement on the underlying theories.  Ha - student has a good grasp on basic practice and begins to branch out and learn from other masters Ri - student develops own practice and creates approaches and adaptations to circumstances Dreyfus Model This model of skill acquisition was published within the scholastic circle, and largely implemented in schools. It is largely individualistic, and familiar to typical teaching styles.  Novice: Concepts are largely distilled, controlled, an...
Read more