My Book - Working For Real: My Book - Working For Realhttps://beta.jimiwikman.se/management/my-book-working-for-real/the-development-phase/?d=21My Book - Working For Real: My Book - Working For RealenWorking with brancheshttps://beta.jimiwikman.se/management/my-book-working-for-real/the-development-phase/working-with-branches-r17/ coming soon

]]>17Fri, 11 Dec 2020 20:26:24 +0000What activities are included in the development phase?https://beta.jimiwikman.se/management/my-book-working-for-real/the-development-phase/what-activities-are-included-in-the-development-phase-r36/
  • Estimation
  • Technical design
  • Accepting requirement
  • Increment Planning
  • Increment startup
  • Daily Alignment
  • Development
    • Control code
    • Atomic Design
  • Development handover
  • Increment Demo/Review
  • Increment Retrospective
    • ]]>    36Sun, 13 Dec 2020 16:17:10 +0000    The many areas that Development supporthttps://beta.jimiwikman.se/management/my-book-working-for-real/the-development-phase/the-many-areas-that-development-support-r63/ As a developer your job is often not just to write code or configure systems. Many times you will be asked to provide technical support for things that are in the planning stages. This includes things like providing technical advice regarding new solutions and to make high level estimations.

    What type of activities are you expected to do outside of development?

     

    ]]>    63Fri, 18 Dec 2020 12:47:46 +0000    Iteration periods - works in any methodologyhttps://beta.jimiwikman.se/management/my-book-working-for-real/the-development-phase/iteration-periods-works-in-any-methodology-r69/ Regardless is you work within a waterfall, RUP, Agile, Lean or any other methodology you have iteration periods. Every methodology call them differently, but they are all the same: a structured and somewhat planned period of time.

    Rather than throwing in different names for these periods, like sprints or delivery cycles, we simply call them: "Iteration Periods". This way we can talk about this across the organization and everyone will know what you are talking about, or at least how that translate to their reality.

    Iteration periods all follow the same basic structure:

    1. You take a moment to evaluate the previous iteration period
    2. You define work that you would like to focus on for the next iteration period.
    3. You ensure that the need of that work is described so that the people in charge of making reality of it feel comfortable taking over responsibility.
    4. You agree on the scope of the next iteration period, and together you start the new iteration period.

    Depending on the methodology these steps may be more or less defined. For example in a Waterfall methodology the scope is well-defined with clear requirements. In an Agile Kanban methodology you focus less on scope and more on available time for say the next month of work. It is still the same four core activities you do: Evaluate, Define, Accept and Proceed.

    ]]>    69Mon, 19 Apr 2021 07:29:25 +0000