thoughts
1. Truly understand the "why" Why should we adopt this new shiny language/framework/database other than that being ... well new & shiny ? Why should we adopt Scrum other than that being recommended by ... so many gurus ? 2. Care to ask "what else ?" Is this the
management
Đây là 1 trong những cái mình thấy quan trọng và khó nhằn nhất khi quản lí 1 team nói riêng hay 1 tổ chức nói chung. Lên kế hoạch để làm thì khá dễ hiểu, tuy nhiên lên kế hoạch sao cho hợp lí, tạo ra giá trị và
insights
Chapter 10, which begins on page 53, lays out the 12 practices that caused our industry to erupt into controversy; and spawned a revolution that has changed everything about the way we write software. Those practices are: The Planning Game: Nowadays known as SCRUM. The idea that software is produced
productmanagement
One of the most common mistakes made on a project is to seize on a feature and call it a requirement without first understanding the problem and the expectations around a solution source
lean
Hôm qua đi hội thảo về Lean Startup nhưng đại khái là cảm thấy chưa thỏa mãn với cách giải thích của các speaker nên mình ghi lại 1 vài suy nghĩ của mình về Lean, bao gồm các điểm chính sau #1: Tóm tắt Mình thấy các bạn ủng
pm
Project Management survival tips some of my tips on how to be a lil bit more effective with Project Management {http://work.plonely.com}
projectmanagement
I found this very true, especially when * I used to focus more on the deployment, but not success (or failure ?) measure and to realize/leverage its value creation * Even when I were to track some measures, the criteria somehow seem a bit blur and not convincing (me) enough Just read
projectmanagement
we just finished the implementation part in a well overdue project, and I want to write 'bout "listening" * there were some problems that were raised even before the testing phase but then de-prioritized (hence forgotten). they did come up later and bit us * there were some good