Skip to content
LinkedIn Twitter RSS GooglePlus
LinkedIn Twitter RSS GooglePlus
Greger Wikstrand
Greger Wikstrand
#agile, #projectmanagement, #ehealth, #mhealth #phr, #professionalism, #SoftwareEngineering
Skip to content
  • Home
  • About
    • Agile Software Development
    • Blog Authors
    • Greger Wikstrand – Publications
    • Images used in this blog
    • My CiteULike Bibliography
Home Posts tagged "work breakdown structure"

Tag: work breakdown structure

You don’t Need User Stories to be Agile

Greger Wikstrand 2012-02-14 2014-01-09Project Management, Requirements Engineering 2

Someone probably told you that you must have user stories to be Agile, right? But really, you don’t need user stories to be agile! I would have you consider what kinds of stakeholders and requirements you have and are trying to meet. Continue reading

Share on:

  • Share on LinkedIn (Opens in new window) LinkedIn
  • Share on X (Opens in new window) X
  • Share on Facebook (Opens in new window) Facebook
  • More
  • Email a link to a friend (Opens in new window) Email
  • Print (Opens in new window) Print
  • Share on Reddit (Opens in new window) Reddit
  • Share on Tumblr (Opens in new window) Tumblr
  • Share on Pinterest (Opens in new window) Pinterest
  • LinkedIn Twitter RSS GooglePlus
  • Top Posts & Pages

    Introduce Agile - the quick fix to a slow team!
    Tired of estimating? Try the goat!
    Extroverted programmers?
    I need help with home automation IoT
    Start managing your risks
    Confirmation bias in software engineering
    Requirements Lifecycles
    Software Development Success
    Where does the information go?
    Alan Shalloway discusses the state of Agile!, part 1 of 3
  • Recent Posts

    • Spring clean your mind
    • Jobs to be done innovation
    • Effective requirements engineering
    • Innovation arenas and outsourcing
    • Cargo cult innovation, play buzzword bingo to spot it
Copyright © 2010-2016 Greger Wikstrand
Powered by Nirvana & WordPress.
LinkedIn Twitter RSS GooglePlus